Application Deployment To Satellite-Linked Communication Nodes

ABSTRACT

Systems, apparatuses, methods, and software are described herein that provide enhanced satellite link-coupled communication nodes. In one example, a parent communication node includes a communication interface configured to communicate with a plurality of child communication nodes over corresponding satellite communication links. The parent communication node includes a resource manager configured to determine physical resources local to each of the plurality of child communication nodes, establish a pool of resources from among the physical resources, and responsive to a request for execution of an application, allocate resources from the pool of resources for execution of the application at one or more selected child communication nodes. The parent communication node can initiate execution of the application using the allocated resources at the one or more selected child communication nodes.

RELATED APPLICATIONS

This application hereby claims the benefit of and priority to U.S.Provisional Patent Application 62/947,233, titled “SATELLITE TO GROUNDEDGE DEVICES AND SYSTEMS,” filed Dec. 12, 2019, which is herebyincorporated by reference in its entirety.

BACKGROUND

Satellite communication systems are emerging as a new mainstreamcommunication medium. Various satellite system operators have begun tolaunch large constellations of satellites into various orbits and designconfigurations, and these constellations can include one or moresatellites that are being positioned to provide end-user communicationservices. End-users, such as enterprise, consumer, and military users,can deploy ground-based satellite communication nodes which communicateover a satellite constellation. Present communications that are carriedby the satellite communication systems largely include special-purposecommunications for commercial and military applications, butincreasingly these communications will include general-purposecommunications, such as Internet access, media streaming, social mediacontent, and web browsing. However, for terrestrial end-user devices,access to satellite constellations typically is limited to singlesatellite system operators and rely upon the infrastructure of thesatellite system operators for the various activities, such as thecommunication, frequency, bandwidth, routing, and reliability of asingle operator. As a result, entities may avoid the use of satellitecommunications, limiting the use of emerging satellite communicationtechnology.

Overview

Systems, apparatuses, methods, and software are described herein thatprovide enhanced satellite link-coupled communication nodes. In oneexample, a parent communication node includes a communication interfaceconfigured to communicate with a plurality of child communication nodesover corresponding satellite communication links. The parentcommunication node includes a resource manager configured to determinephysical resources local to each of the plurality of child communicationnodes, establish a pool of resources from among the physical resources,and responsive to a request for execution of an application, allocateresources from the pool of resources for execution of the application atone or more selected child communication nodes. The parent communicationnode can initiate execution of the application using the allocatedresources at the one or more selected child communication nodes.

This Overview is provided to introduce a selection of concepts in asimplified form that are further described below in the TechnicalDisclosure. It should be understood that this Overview is not intendedto identify key features or essential features of the claimed subjectmatter, nor should it be used to limit the scope of the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the disclosure can be better understood with referenceto the following drawings. While several implementations are describedin connection with these drawings, the disclosure is not limited to theimplementations disclosed herein. On the contrary, the intent is tocover all alternatives, modifications, and equivalents.

FIG. 1 illustrates a communication environment according to animplementation.

FIG. 2 illustrates example operations for a communication systemaccording to an implementation.

FIG. 3 illustrates example operations for a communication systemaccording to an implementation.

FIG. 4 illustrates a communication environment according to animplementation.

FIG. 5 illustrates communication layers according to an implementation.

FIG. 6 illustrates a communication environment according to animplementation.

FIG. 7 illustrates a communication environment according to animplementation.

FIG. 8A illustrates example operations for a communication systemaccording to an implementation.

FIG. 8B illustrates example operations for a communication systemaccording to an implementation.

FIG. 9 illustrates a parent node according to an implementation.

FIG. 10 illustrates a child node according to an implementation.

DETAILED DESCRIPTION

Operators of satellite communication systems can deploy one or moresatellite devices which operate independently or form constellations ofsatellite devices in various orbits and design configurations forcommunication services. End-users can deploy various terrestrial nodes,including stationary, mobile, seafaring, airborne mobile, or tetheredairborne nodes which communicate over satellite communication linksprovided by a corresponding satellite communication system. Thesesatellite communication links can transport specialized communicationsor general-purpose packet communications, such as Internet access, mediastreaming, and web browsing. Moreover, terrestrial communication nodescan be placed over various geographic areas to provide sensing ortelemetry services, and associated data can be backhauled over thesatellite communication links. These sensing and telemetry servicesmight employ sensors, sensing devices, Internet-of-Things (IoT) devices,or other devices local to an associated terrestrial communication node.The examples herein discuss various terrestrial communication nodes,communication systems, and control techniques to provide enhancedcommunication services to end-users that employ satellite communicationlinks.

In a first example, FIG. 1 is presented. FIG. 1 includes communicationenvironment 100 having various communication nodes comprising parentnode 110 and child nodes 120, 130, and 140. Each child node comprises anassociated satellite communication interface 181-183, and each childnode can communicate over at least one satellite communication link. Twoexemplary satellite communication links 177-178 are shown for child node120. These satellite communication links are provided by one or moresatellite communication service providers, such as a first orbitalsatellite group 150 and a second orbital satellite group 151 havingsatellite devices 152-153 and 154-155, respectively. Parent node 110includes satellite communication interface 180 and communicates over oneor more satellite communication links, shown in FIG. 1 as exemplarylinks 175-176. Parent node 110 also communicates with packetcommunication system 160 over communication link 170. Data services161-162 illustrate various cloud computing, distributed data storage, ordata handling services which may be employed by other elements ofenvironment 100. Data services 161-162 communicate over communicationlinks 171-172, respectively.

In operation, parent node 110 establishes communication arrangementswith one or more child nodes over satellite communication links,referred to as satellite edge networks (SENs). These SEN communicationarrangements can include various local area network (LAN) or wide areanetwork (WAN) arrangements, as well as various communication links. InFIG. 1, SEN 102 is formed over various satellite communication links tocouple parent node 110 and one or more among child nodes 120, 130, and140 in a SEN arrangement. Moreover, parent node 110 can establish one ormore connections or routes to other external systems over one or morenetwork links including link 170. SEN 102 can thus span over one or moresatellite communication links, one or more satellite groups or satellitecommunication service providers, one or more network arrangements, andone or more child nodes. Child nodes 120, 130, and 140 can be coupled toeach other over an associated SEN arrangement, or over one or more links184-185. Child nodes 120, 130, and 140 can be coupled to one or moreobject nodes coupled over associated local communication interfaces 124,134, and 144, which might comprise network interfaces, point-to-pointelectrical interfaces, wireless interfaces, or optical interfaces, amongothers, including combinations thereof. In FIG. 1, child node 120 iscoupled to object nodes 121-123, child node 130 is coupled to objectnodes 131-133, and child node 140 is coupled to object nodes 141-143.Child nodes 120, 130, and 140 can transfer data over one or moresatellite links, among other links discussed herein, which may includecommunication involving more than one satellite or satellite linkconcurrently, bonded, or in a broadcast manner, with one or moresatellites configured to route traffic of the child nodes to variousdestinations including additional satellites.

Each child node might be located in a same or different geographiclocation with respect to each other, and these different locations mightcorrespond to visibility to different satellites at any given time. FIG.1 shows three locations (2, 3, 4) which are distinct from each other andfrom location 1 of parent node 110. Although stationary child nodes areshown in FIG. 1 for clarity, any of these child nodes might insteadcomprise mobile nodes associated with a mobile and/or relocatable userdevice, ground surface vehicle, watercraft, ship, submersible, othersatellite devices, or airborne vehicle. Nodes might bestationary/tethered into place, or may be in motion, includingcombinations thereof. Additionally, one or more child devices might beco-located at a similar or same geographic location or within the samedevice or mobile entity.

FIG. 2 is presented to illustrate example operations 200 of the elementsof FIG. 1. In FIG. 2, connectivity of parent node 110 and child nodes120, 130, and 140 is established (210) with at least satellitecommunication links communicatively coupling parent node 110 to selectedchild nodes 120, 130, and 140. The satellite communication linksestablish at least a link layer connection using satellite communicationlinks provided by satellite communication service providers, such asthat of satellite group 150 or satellite group 151. Each communicationnode among parent node 110 and child nodes 120, 130, and 140 canindependently establish link connectivity with a satellite communicationsystem over satellite communication links of satellite group 150 orsatellite group 151.

Once connected, then a logical relationship or SEN relationship amongparent node 110 and selected child nodes 120, 130, and 140 isestablished by parent node 110. Parent node 110 can discover one or morechild nodes located remotely from parent node 110. Discovery of thechild nodes might be predetermined such as by indicating parameters ofeach child node to parent node 110, which might include networkaddresses, node identifiers, or other parameters which allow for trafficexchange between parent node 110 and associated child nodes. In otherexamples, parent node 110 performs a discovery process over satellitecommunication links which couple to each child node. Once selected childnodes are discovered or identified by parent node 110, then parent node110 initializes each child node into a desired arrangement, such as aSEN arrangement.

Specifically, in FIG. 2, parent node 110 initiates (211) parent node andchild node relationships. These relationships comprise logicalcorrespondences among various communication nodes which define parentnode 110 as a primary node which controls operations and maintainscommunication arrangements with one or more secondary nodes selectedamong child nodes 120, 130, and 140. Typically, parent node 110establishes a SEN arrangement with selected child nodes, which mightinclude establishing a network transport layer (or higher layers in anetwork stack) to service a SEN relationship among parent node 110 andselected child nodes. Moreover, parent node 110 can deploy softwareelements, such as applications, to child nodes, as well as instructchild nodes on connectivity adjustments or communication link changes,among other command and control functions. Parent node 110 might beconfigured by a network operator or network manager with one or moreparameters or instructions that indicate or identify which child nodesshould be included in a parent-child arrangement, as well as otherparameters that configure SEN arrangements among such nodes.

Parent node 110 is shown in FIG. 1 as predetermined as a parent node.However, the functionality and features that define a parent node assuch might be portable or transferrable. In one example, parent nodefunctionality can be taken over by a child node, where that child nodecan be elevated from a subordinate node into a parent node. The parentnode functionality might be encapsulated into one or more softwareobjects accompanied by state information. The software objects mightcomprise one or more applications, virtualized applications, containers,virtual nodes, or other configurations. The state information caninclude information identifying child nodes, status of the various childnodes, satellite communication link status and identifiers, networkaddressing information for communication nodes, failure informationrelated to why a previous parent node failed, object node locations andproperties, resources at child nodes, and pool resource information,among other information. In addition, the state information mightinclude a current state of SEN 102 indicating child/parent node members,locations, activity status, network addressing, link configurations,deployed applications, used/free resources, and other information.Failure of a parent node can trigger a child node to take over andresume the activities and function of the failed parent node.Non-failure transfers of role from child to parent can also occur, suchas when a parent node experiences reduction in communication linkbandwidth or availability, planned outages, user-initiated role changes,or other triggers.

During operation of the communication nodes, each communication nodemonitors (212) properties of a satellite communication link or linkswhich communicatively couple the communication nodes into thearrangement established in operation 211. For example, parent node 110and child nodes 120, 130, and 140 might be arranged into SEN 102 whichcomprises a network transport layer separate from or in addition to anyprovided by satellite communication service providers. To couple intoSEN 102, each communication node employs an associated satellitecommunication link. However, each individual satellite communicationlink might experience various changes in link properties or link statusover time. The changes in the properties of the satellite communicationlinks can indicate a communication link quality falling below a qualitythreshold or a link status not meeting one or more criteria such as biterror rate, data rate, latency, or other parameters. These changes mightaffect connectivity or communications carried by each satellitecommunication link and by SEN 102 as a whole. Moreover, deployedapplications or control instructions initiated by parent node 110 tochild nodes might experience difficulty in deployment, execution, orcompletion when properties of the satellite communication links change.

At least a portion of the link monitoring activities of operation 212might instead be performed by the satellite communication serviceproviders which provide the satellite communication links. Many times,the satellite communication service providers monitor link status forall connected devices or nodes, and can determine when link statuschanges from a physical layer or link layer, among other layers of anetwork stack or protocol stack. FIG. 5 illustrates some example networkstack arrangements, and the satellite communication service providersmight be tasked with monitoring performance, status, and operation forlayers L1 and L2. The satellite communication service providers can thenprovide indications of the performance, status, and operation for layersL1 and L2 to one or more of the communication nodes of FIG. 1. In someinstances, satellite communication service providers can makeadjustments to the satellite communication links and notify thecommunication nodes of FIG. 1 of the adjustments.

Monitored link properties can include link signal strength, linkavailability, link carrier frequency, link center frequency, linkmodulation type, link spreading scheme, link bandwidth, link powerlevel, link channelization property, link latency, link routing, asatellite communication services provider of the link, orbitalconfiguration of satellites providing the link, link security measures,link protocol, link compression type, link quantity, and other linkproperties which might change over time. To monitor the link propertiesof the satellite communication links, each communication node caninclude a link manager. In FIG. 1, parent node 110 includes link manager111, while child node 120 includes link manager 125. Other child nodescan include similar elements as child node 120, and these elements areomitted in FIG. 1 for clarity. Link manager 111 and link manager 125 canmonitor link properties or signal properties for associated satellitecommunication links. Link manager 111 can monitor satellitecommunication links 175-176, and link manager 125 can monitor links177-178. Link manager 111 and link manager 125 can share monitoringduties for the various links in FIG. 1.

In addition to link properties, requirements for applications deployedto child nodes or executed by child nodes can also be monitored (213).Child node 120 shows applications 127 deployed by parent node 110. Otherchild nodes can have similar configurations. Each child node includes apolicy engine to perform monitoring of deployed applications. FIG. 1shows policy engine 126 for child node 120, and child nodes 130 and 140can include similar features. Parent node 110 might include policyengine 112 to perform similar functionality to that of the policyengines of each child node. The application requirements might includeproperties, status, or physical components preferred or required forexecution of an application at a child node or execution of anapplication across more than one child node. The applicationrequirements can include communication properties preferred or requiredfor execution of the one or more applications or for transfer of data bythe child node which can be related to the one or more applications.These various application requirements can comprise a user policyassociated with the one or more applications, an application protocolemployed by the one or more applications, an anticipated change incommunication or communication needs of the one or more applications, acommunication reliability requirement of the one or more applications, acommunication performance requirement of the one or more applications, acommunication bandwidth requirement of the one or more applications, acommunication latency requirement of the one or more applications, and acommunication legality or government regulation associated with the oneor more applications, among other requirements or preferences forapplications.

Policy engine 126 determines (214) if one or more link policy conditionsor link triggers have been met while monitoring the link propertiesdetermines (216) if one or more application policy conditions orapplication triggers have been met while monitoring the applicationrequirements. Turning first to the link policy conditions or linktriggers, the one or more link conditions or link triggers can promptpolicy engine 126 to initiate changes via link manager 125 to the one ormore satellite communication links. In addition to the criteria,requirements, status, or thresholds for properties mentioned above, theone or more link triggers might also comprise at least one among asignal strength threshold for the one or more satellite communicationlinks, a link availability status change for the one or more satellitecommunication links, jamming conditions for the one or more satellitecommunication links, and a preemption activity affecting the one or moresatellite communication links, among other triggers. Preemptionactivities can include government preemption for usage of communicationlinks or satellites, commercial preemption of communication links orsatellites for higher-priority entities or users, or preemption relatedto maintenance and administrative activities for the communication linksor satellites.

In response to the link conditions or triggers, policy engine 126 enactschanges (215) to the satellite link or to one or more satellite linkproperties by instructing link manager 125 in accordance with thechanges. Altering the properties of the one or more satellitecommunication links can include changing a the satellite communicationlink to a different communication link or altering at least one among aphysical communication pathway, a communication link frequency, acommunication link modulation type, a communication link bandwidth, acommunication link power level, a communication link channelizationproperty, a communication link latency, a communication link routing,and a satellite network providing the one or more satellitecommunication links, among other alterations. Operation of policy engine126 may include link management and link changes at a link layer, andmight instead include link management or changes at a ‘higher’ layer ofa network stack or protocol, such as seen in FIG. 5. Furthermore, linkmanager 125 might enact the changes to the satellite link properties byindicating desired changes to a satellite communication service providerwhich responsively initiates the changes.

In one example, responsive to changes in properties of a satellitecommunication link indicating a communication link quality falling belowa quality threshold or not meeting a policy-based preference, policyengine 126 is configured to select a different communication pathway ordifferent communication link to accommodate at least the communicationrequirements. In FIG. 1, a first satellite communication link for childnode 120 includes link 177 which is provided by orbital satellite group150. Link 177 might be an initial link established for child node 120and having initial properties which support a particular set ofapplication requirements. However, changes in the properties orapplications requirements can trigger changes to link 177. These changesmight include various changes to the link properties discussed above,such as a different communication frequency, different bandwidth,different power level, different gain, different communication codingscheme, different data or signal compression scheme, different routing,or different beam alignment, among other changes. However, these changescan also include changing to a second communication link provided by thesame satellite, a different satellite, or a different satellitecommunication service provider, as well as changing to a differentcommunication beam. The second communication link might comprise link178 established with orbital satellite group 151.

Thus, policy engine 126 might select a different communication pathwayand different satellite communication service provider than that of link177 to accommodate at least the communication requirements orapplication requirements. Policy engine 126 might direct link manager125 to discontinue satellite communication link 177 and communicate oversatellite communication link 178. Policy engine 126 might instead directlink manager 125 to establish a combined communication bandwidthassociated with satellite communication link 177 and satellitecommunication link 178. Link manager 125 can provide the combinedcommunication bandwidth of links 177 and 178 to at least an applicationof child node 120 that is associated with the communicationrequirements. Although link 178 is shown as a different satellite-basedcommunication link selected for communication node 120, a differentselected communication pathway can instead comprise a communication linkprovided by an airborne node or terrestrial node that has linkavailability with orbital satellite group 150/151 or a terrestrialcommunication network.

The one or more application triggers might also comprise at least oneamong a change in execution status of the one or more applications,anticipated application execution, presence of newly deployedapplications, or change in communication link status to supportactivities of one or more applications. Application triggers can promptpolicy engine 126 to trigger (217) application operations. Policy engine126 can initiate execution of one or more applications or initiateactivities of one or more executing applications based on theapplication triggers. Certain applications or certain functions of theapplications might prefer or require certain communication linkproperties, such as bandwidth, power, data rate, encryption type,satellite, latency related to link distance, communication provider,time of day, or other link properties. Policy engine 126 can determinewhat activities are supported by present communication link properties,and enable or initiate application operations based on these presentproperties. One example includes starting a video data downloader whenthere is sufficient available bandwidth of a communication link and thepresent time of day is not during a peak timeframe. Another exampleincludes policy engine 126 to inhibit data transfer for one or moreapplications while enabling data caching functionality for that datawhen communication link bandwidth power, or availability is below atarget threshold level. Policy engine 126 can initiate transfer ofportions of the cached data or instruct applications to bundle data forburst transfer periodically or responsive to communication linkbandwidth being above a target threshold level or during certain timesof day or days of the week. In yet a further example, quality of service(QoS) for applications can be considered, and when QoS levels are notbeing met, then link or application changes might be performed. Policyengine 126 or other elements might monitor QoS metrics and triggerchanges to applications, links, or operations based on these QoSmetrics.

Turning now to further example operations 300 for the elements of FIG.1, a method of operation is presented in FIG. 3. The operations in FIG.3 relate to operation of child nodes with respect to a parent node andhandling of data generated by object nodes coupled to child nodes. InFIG. 3, operations are discussed in the context of child node 120, butit should be understood that other child nodes might instead beemployed.

Child node 120 identifies (310) object nodes local to child node 120.These object nodes can include various sensors, sensor devices,telemetry devices, Internet of Things (IoT) devices, control equipment,user devices, user equipment, displays, or other devices, which might beassociated with other users or separate networks, comprising similarequipment as above. Object nodes 121-123 are included in FIG. 1 andcoupled over one or more links represented by link 124. Child node 120receives (311) data from operation of object nodes 121-123, such astelemetry data, sensor data, IoT data, and the like. This data might beincluded in one or more data packets or data portions that arrive inchild node 120 according to the protocol and link properties of link124. For example, if link 124 comprises a wireless link, then the datapackets can be received over a wireless communication interface.Likewise, if link 124 comprises a wired link such as Ethernet, then thedata packets might be received over a network interface.

Responsive to receiving the data packets, child node 120 processes (312)the data packets, such as by inspecting properties of headers orpayloads. From this inspection, child node 120 determines (313) targetlocations of data recipients for the data packets. When local sensors ortelemetry devices are employed, such as IoT devices, then data relatedto operation of the IoT devices might be consumed locally by the childnode or transferred by the IoT devices to a data consumer nodecomprising a recipient node or collection node. However, this dataconsumer node might be located remotely from child node 120 or might belocated in a similar location as child node 120. In other examples, thedata might be transferred to parent node 110 for storage, processing, orother handling by parent node 110. Child node 120 performs adetermination process on the data packets to determine if the datapackets should be routed to a local target or a remote target (314). Ifa local target is identified for the data packets, then child node 120routes (315) the data packets to a local node for initiation of a localalert (316). This local alert can be related to operations of thesensors or telemetry devices coupled to child node 120.

If a remote target is identified for the data packets, then child node120 routes (317) the data packets over a satellite communication link toparent node 110. Parent node 110 might further route the data packetsfor delivery to an destination node that consumes (320) the datacomprising a data ‘consumer’ node. This data consumer node might be acollection node or recipient node operated by parent node 110, might bea further child node, or might comprise yet a further node coupled overpacket communication system 160. When the data packets are for use inparent node 110 (318), then parent node 110 can consume (319) the datapackets or data carried by the data packets. The consumption of the datain parent node 110 refers to storing the data or the data packets,processing the data or the data packets, or otherwise operating on thedata or the data packets. In one example, parent node 110 might host anapplication which consumes the data of the data packets. In anotherexample, parent node 110 might cache or store the data packets for aperiod of time before forwarding the data packets to a data consumernode when conditions warrant. These conditions can include governmentregulation, bandwidth, or power constraints of further communicationlinks, time of day or day of the week, or to await further data portionsfrom one or more child nodes. Parent node 110 might collect data packetsuntil a threshold amount of data has been received before forwarding thedata to a data consumer node. Parent node 110 might further cache datafor delivery to other child nodes, such as when parent node cachescontent that a first child node has provided for use by other childnodes.

In one example, child node 120 is configured to provide data related tooperation of one or more local telemetry devices over SEN 102 forreceipt by parent node 110, where SEN 102 comprises one or moresatellite communication links shown in FIG. 1. Parent node 110 isconfigured to parse traffic received from child node 120 and route atleast a portion of the data related to the operation of the one or morelocal devices that source telemetry to at least one additional childnode coupled to SEN 102 over an additional satellite communicationpathway. For example, the additional child node might comprise childnode 130, and child node 130 can couple to SEN 102 over a correspondingsatellite communication link. Telemetry data or sensor data thatoriginates at child node 120 or a location of child node 120 can berouted by parent node 110 over one or more satellite communication linksfor delivery to child node 130. A user or operator at child node 130 canbe alerted to the telemetry data or sensor data. Child node 130 mighthave one or more applications deployed thereto which consume (317) thetelemetry data or sensor data originated by object nodes at child node120. Thus, parent node 110 can facilitate transfer of the dataoriginated at child node 120 to another child node executing data whichemploys such data in one or more applications. These applications mightbe executed by child node 130 or by one or more object nodes coupled tochild node 130, and comprise monitoring applications, factory automationapplications, agriculture operations applications, mining operationsapplications, electrical power generation and distribution applications,residential connection applications, or any other industrial, military,or commercial application which employs sensor/telemetry data generatedat a first location and first child node for consumption at a secondlocation and second child node. The network arrangement established byparent node 110 over the corresponding satellite communication links canfurther enable such operations among object nodes and child nodes.

In a further example, data generated at child node 120 might beaddressed for transfer to child node 130 or an object node at child node130 or over packet communication system 160. However, the data might berelated to sensors or telemetry devices local to child node 120. Anoperator nearby child node 120 might desire to be notified of certainissues related to the data, even if an application is still configuredto monitor/consume the data at another location. Child node 120 orparent node 110 can parse traffic that carries this data and determineif a local operator or operator device coupled to child node 120 shouldbe alerted, as in operation 315. An operator local to child node 120 canthus be deployed to respond to problems, sensor data anomalies,failures, out-of-bounds conditions, or other alert conditions at alocation of child node 120 without the data having to be delayed bytransfer to another remote node and associated remote alerts dispatchedto the location of child node 120. In such examples, an on-sitetechnician can be alerted locally to problems or issues worthy ofinspection or maintenance as indicated by locally generated data whilethe same data is transferred to a collection or monitoring node remotefrom the locality. A copy or mirror of the data might be produced bychild node 120 or parent node 110 to support this bifurcated transferscheme. Headers of traffic or metadata associated with traffic generatedby sensors or telemetry devices might be monitored by child node 120 orparent node 110 for detection of relevant traffic that should be routedfor local alerts. These headers might include flags or indicatorsrelated to status or alert presence, as well as network addresses orother identifiers which can identify the sensor or telemetry device thatgenerated the data.

Returning to the elements of FIG. 1, parent node 110 includes linkmanager 111 and policy engine 112. Parent node 110 also comprises one ormore computing systems comprising one or more processing devices,storage devices, and communication interfaces (such as satellitecommunication interface 180). Further examples of parent node 110 areillustrated in FIG. 9. In some examples, parent node 110 comprises oneor more user terminals such as Very Small Aperture Terminals (VSAT)devices, electronically steered terminal devices, hybrid terminaldevices, or other terminal devices and types (also referred to herein asedge antennas) configured to communicate with one or more satellitecommunication service providers. A first communication interface 180 ofparent node 110 can include a satellite communication interfaceconfigured to communicate over one or more satellite communicationlinks, such as links 175-176. A second communication interface of parentnode 110 can include a terrestrial communication interface which mightcomprise a network interface, wireless communication interface, wiredcommunication interface, or optical communication interface configuredto communicate over one or more packet links, such as communication link170. In some examples, parent node 110 comprises network router, bridge,and firewall circuitry or elements. The various communication interfacescan include transceivers, RF circuitry, antenna elements, upconverters,downconverters, amplifiers, mixers, multiplexers, demultiplexers,connectors, and other similar communication equipment. Parent node 110includes circuitry and processing elements to operate as discussedherein, such as discovering and managing child nodes, managing satellitelink properties and connections, managing pools of resources found atchild nodes, deploying applications to child nodes, selectively routingtelemetry or sensor data generated at child nodes, and deploying data orapplications to child nodes for edge caching, among other operations.

Child nodes 120, 130, 140 can each comprise a link manager, policyengine, and one or more applications. Child node 120 is shown in FIG. 1as including exemplary link manager 125, policy engine 126, andapplications 127. Further configurations of child nodes are shown inFIG. 10. Child nodes 120, 130, 140 also comprise one or more computingsystems comprising one or more processing devices, storage devices, andcommunication interfaces (such as satellite communication interfaces180-182). In some examples, child nodes 120, 130, 140 might comprise oneor more edge antenna devices configured to communicate over one or moresatellite communication service providers. Child nodes 120, 130, 140each comprise at least one satellite communication interface 180-182,and many examples include more than one instance of a satellitecommunication interface to support concurrent communication over morethan one satellite communication link and with more than one satellitecommunication services provider. Each child node also includes one ormore other communication interfaces for communication with object nodes.A first communication interface of child nodes 120, 130, 140 can includea satellite communication interface configured to communicate over oneor more satellite communication links, such as links 177-178. A secondcommunication interface of child nodes 120, 130, 140 can include aterrestrial communication interface which might comprise a networkinterface, wireless communication interface, wired communicationinterface, or optical communication interface configured to communicateover one or more packet links, such as links 124, 134, and 144. In someexamples, child nodes 120, 130, 140 comprise network router, bridge, andfirewall circuitry or elements. The various communication interfaces caninclude transceivers, radio frequency (RF) circuitry, antenna elements,upconverters, downconverters, amplifiers, mixers, multiplexers,demultiplexers, connectors, and other similar communication equipment.

Child nodes 120, 130, 140 each include circuitry and processing elementsto operate as discussed herein, such as communicating with a parent nodein a network arrangement, managing link properties and connectivityproperties, monitoring link status or connectivity status, monitoringapplication requirements, caching data or applications for use by otherchild nodes, executing locally deployed applications, storing data forlocally executed applications or for coupled object nodes, communicatingwith object nodes and managing traffic generated by object nodes, amongother operations. As discussed above, any of child nodes 120, 130, or140 might take over at least a portion of the role or functionality ofparent node 110. In such instances, child nodes 120, 130, or 140 mightcomprise circuitry, software, features, or elements to provide for atleast the portion of parent node 110.

Object nodes 121-123, 131-133, 141-143 each comprise processingcircuitry, memory and storage elements, and one or more communicationinterfaces. Object nodes 121-123, 131-133, 141-143 might comprisetelemetry gathering devices or systems that sense or gather data relatedto particular pieces of monitored equipment, machines, or nearbyenvironments. Object nodes 121-123, 131-133, 141-143 might comprisesensor devices, data observation nodes, user equipment, user devices, orother equipment. Object nodes 121-123, 131-133, 141-143 can includesensors, such as motion sensors, imaging sensors, heat sensors, thermalsensors, thermostats, electromagnetic spectrum sensors, power sensors,electrical current sensors, laser sensors, proximity sensors, seismicsensors, meteorological sensors, chemical sensors, nuclear radiationsensors, pressure sensors, material or fluid flow rate sensors, speed orrotation sensors, accelerometer sensors, magnetometer sensors, barometersensors, or other sensors, including combinations thereof. Object nodes121-123, 131-133, 141-143 might comprise user equipment or user devices,such as smartphones, tablet computers, laptop computers, desktopcomputers, gaming console, or other computing and communication devices,whether stationary or mobile. In some examples, object nodes 121-123,131-133, 141-143 comprise IoT devices, each with a particular duty orfunction which can communicate over a communication interface with achild node. Object nodes 121-123, 131-133, 141-143 might comprisecircuitry and equipment to receive signals corresponding to one or moreposition, navigation, and timing (PNT) systems such as global navigationsatellite system (GNSS) systems, including Global Positioning System(GPS), Global Navigation Satellite System (GLONASS), BeiDou NavigationSatellite System (BDS), or Galileo system, among others includingPNT-enhancing systems such as European Geostationary Navigation OverlayService (EGNOS) or Wide Area Augmentation System (WAAS).

Object nodes 121-123, 131-133, 141-143 communicate over objectcommunication links 124, 134, 144. Links 124, 134, 144 can use metal,glass, optical, air, space, or some other material as the transportmedia. Links 124, 134, 144 can use various communication interfaces andprotocols, such as Internet Protocol (IP) versions 4 or 6, Ethernet,universal serial bus (USB), Wireless USB, Thunderbolt, Bluetooth, IEEE802.11 (WiFi), WiMAX (Worldwide Interoperability for Microwave Access),microwave RF communications, High Frequency (HF), Very High Frequency(VHF) communications, ultra high frequency (UHF) communications,low-power wide-area network (LPWAN), LoRa (Long Range), low-ratewireless personal area networks (LR-WPANs), IEEE 802.15.4 (Zigbee, amongothers), Near-field communication (NFC), Infrared Data Association(IrDA), or other communication signaling or communication formats,including combinations, improvements, or variations thereof. Links 124,134, 144 can be direct links or may include intermediate networks,systems, or devices, and can include a logical network link transportedover multiple physical links.

Links 184-185 are included in FIG. 1 to show optional child-to-childcommunication links. Links 184-185 might comprise wired or wirelesslinks, RF or optical links, or other link configurations described abovefor any of links 175-178 and 124, 134, and 144, among other link types.For example, links 184-185 might comprise cellular or wireless linksthat couple child nodes over a cellular communication system orcustom-deployed wireless network. In other examples, wired or hybridwired-wireless communication links are employed which comprise one ormore packet networks. When links 184-184 are included, then theassociated child nodes can include communication interfaces to supportsuch links, which might include further transceivers, network interfacecards, optical communication equipment, and the like. In furtherexamples, links 184-185 might comprise logical or virtual linkstransported over one or more satellite communication links to form acommunication connection between corresponding child nodes. Theselogical or virtual links employ portions of satellite devices or parentnode 110 to route traffic from one child node to another child node.Virtual private network (VPN) or tunneling arrangements can also beemployed to form links 184-185.

Orbital satellite groups 150-151 each comprise separate collections orconstellations of one or more satellite devices deployed into orbits anddesign configurations about a central mass, such as the Earth, ahuman-made orbiting object such as a space station, other satellites ina swarm configuration, an orbital lunar outpost, or other celestialobjects or planets. Satellite devices of each orbital satellite groupmight share a common orbit or orbital configuration, which might formplanes, rings, or other arrangements. Each orbital satellite group mightcorrespond to a single communication services provider, satelliteoperator, government entity/operator, private or public company, orother organization/entity which employs a particular communicationfrequency or set of frequencies for satellite devices of that particularorbital satellite group. Orbital satellite group 150 includes satellitedevices 152-153, and orbital satellite group 151 includes satellitedevices 154-155. Satellite devices 152-155 can comprise various hardwareand software elements included in an orbital package. Satellite devices152-155 can comprise communication equipment, processing equipment, andcontrol/logistical elements including structures, mechanisms,propulsion, attitude control, power generation and management, andthermal management elements. Satellite devices 152-155 includecommunication equipment and antenna elements to communicate with one ormore ground devices and/or other satellites, such as shown for parentnode 110 and child nodes 120, 130, and 140. The antenna elements mightbe omni-directional, directional, or orientable according to locationsof surface or airborne devices, such as using gimbal mounts, servos,phased arrays, or other features. Inter-satellite communications mightoccur using RF or optical communications. Satellite devices 152-155 canbe deployed into various orbits, each corresponding to a particularorbital configuration. Although exact definitions can vary, low-earthorbits (LEO) typically comprise orbital altitudes of 2,000 kilometers(km) or less, and medium-earth orbits (MEO) typically comprise orbitalaltitudes of 2,000 km up to geosynchronous (GSO) orbital altitudes of35,786 km. A geostationary orbit is a special case of a GSOcorresponding to a geosynchronous orbit about the equator (e.g. at zerodegrees inclination), and can be referred to as a geosynchronousequatorial orbit (GEO). Non-geosynchronous (NGSO) orbits can includethose not defined as GSO or GEO. Other example orbits include High EarthOrbits and critically-inclined orbits. These specific definitions oforbital altitudes can vary based on the particular defining entity anddeployed configuration. Other orbital configurations are possible, whichmight have various inclinations and altitudes, such as equatorial andpolar orbits. Although the term “geo” is typically assigned toEarth-centric orbits, it should be understood that the orbitalconfigurations and definitions herein might instead be applied to otherbodies, such various planets, moons (e.g. lunar-centric), and sun/stars(e.g. helio-centric).

Satellite communication links 175-178 each comprise a particular set ofparameters that may include center frequency, bandwidth, power setting,channel, channel set, frequency, frequency set, center frequency, orfrequency spread, among others. While implementations of satellitecommunication links 175-178 are not limited to a particular frequencyrange, some implementations may utilize a frequency range correspondingto the Institute of Electrical and Electronics Engineers (IEEE) bands ofL band, S band, C band, X band, Ku band, Ka band, V band, W band, amongothers, including combinations thereof. Other example communicationfrequency ranges and service types include ultra-high frequency (UHF),super high frequency (SHF), extremely high frequency (EHF), or otherparameters defined by different organizations such as broadcastsatellite service (B S S), fixed-satellite service (FSS),mobile-satellite service (MSS) or similar services for communications.

In addition to satellite-to-ground links shown for links 175-178,additional satellite-to-satellite links might be included. These linksare represented by link 179 in FIG. 1 and can include communicationlinks between satellites of the same orbital satellite group or amongdifferent orbital satellite groups. Moreover, various constellations orswarm patterns or arrangements of satellites can be formed, and thesearrangements can have various communication topologies for transferringcommunications between satellites. In-plane and cross-planecommunications can be provided when satellites are arranged intogroupings comprising orbital rings or planes. Link 179 can comprise anyof the links described herein for links 175-178, which might include RF,optical, laser, or other similar communication links, among others.

Packet communication system 160 comprises one or more packet networksconfigured to route packet communications between endpoints over networklinks. Packet communication system 160 can include routers, bridges,switches, management systems, network links, and other network routingand handling equipment, including combinations thereof. In someexamples, packet communication system 160 comprises one or morelong-haul communication service providers that route packetcommunications over network links between local internet serviceproviders (ISPs) that provide last-mile services to end users or datacenters.

Data services 161-162 each comprises server based or distributedcomputing based data services and platforms, such as database services,messaging services, application services, or control system services,among others. Data services 161-162 can each include communicationinterfaces, network interfaces, processing systems, computer systems,microprocessors, storage systems, storage media, or some otherprocessing devices or software systems, and can be distributed amongmultiple devices or across multiple geographic locations. Examples ofdata services 161-162 can each include software such as an operatingsystem, logs, databases, utilities, drivers, networking software, andother software stored on a computer-readable medium. Data services161-162 can each comprise one or more platforms which are hosted by adistributed computing system or cloud-computing service. Data services161-162 can each comprise logical interface elements, such as softwaredefined interfaces and Application Programming Interfaces (APIs). Dataservices 161-162 can each include one or more user interfaces, such asgraphical user interfaces, web interfaces, APIs, terminal interfaces,console interfaces, command-line shell interfaces, extensible markuplanguage (XML) interfaces, among others.

Communication links 170-172 can each represent one or more communicationlinks, such as one or more network links comprising wireless or wirednetwork links. Communication links 170-172 can comprise various logical,physical, or application programming interfaces. Example communicationlinks can use metal, glass, optical, air, space, or some other materialas the transport media. Communication links 170-172 can use variouscommunication protocols, such as Internet Protocol (IP), Ethernet,hybrid fiber-coax (HFC), synchronous optical networking (SONET),asynchronous transfer mode (ATM), Time Division Multiplex (TDM),Long-Term Evolution (LTE), 3rd Generation Partnership Project(3GPP)-defined protocols, 5G or 5G NR (New Radio) communications,circuit-switched, communication signaling, wireless communications, orsome other communication format, including combinations, improvements,derivatives, or variations thereof. Communication links 170-172 caninclude direct links or may include intermediate networks, systems, ordevices, and can include a logical network link transported overmultiple physical links. Communication links 170-172 can includerouters, switches, bridges, traffic handling nodes, and the like fortransporting traffic among endpoints.

FIG. 4 illustrates communication environment 400 according to animplementation. In FIG. 4, several elements found in FIG. 1 areincluded, along with additional elements used to illustrate furtherexample implementations. However, it should be understood that theexamples in FIG. 4 are not limited to the elements found in FIG. 1. FIG.4 illustrates various communication pathways for child nodes and parentnodes to form and communicate over satellite edge network (SEN) 402.Communications between child nodes and parent nodes might be routed overany of the various links or pathways discussed in FIG. 4. FIG. 4includes parent node 110, child nodes 120 and 420, airborne node 430,and two orbital satellite groups 150-151. Airborne node 430 comprisesone or more airborne or atmospheric nodes, such as aircraft, airplanes,drones, unmanned aerial vehicles (UAVs), balloons, or other similarairborne vehicles, can be tethered/stationary or mobile. Child nodes 120and 420 are communicatively coupled via terrestrial communication link480, which also communicatively couples a plurality of object nodes421-423.

Parent node 110 can communicate with orbital satellite group 150 oversatellite communication link 470 and communicate with orbital satellitegroup 151 over satellite communication link 471. In some examples,parent node 110 uses only one link among links 470 and 471 forcommunications. In other examples, parent node 110 can communicate overboth links 470 and 471 concurrently, or merge both links 470 and 471into aggregated communication pathway 472. Child node 120 cancommunicate with orbital satellite group 150 over satellitecommunication link 473 and communicate with orbital satellite group 151over satellite communication link 474. In some examples, child node 120uses only one link among links 473 and 474 for communications. In otherexamples, child node 120 can communicate over both links 474 and 475concurrently, or merge both links 474 and 475 into aggregatedcommunication pathway 475. Child node 420 can communicate with eitherorbital satellite group 150 or orbital satellite group 151 oversatellite communication link 476. Child node 420 can also communicatewith one or more airborne nodes, such as airborne node 430, overcommunication link 478. Airborne node 430 can communicate with childnode 420 over communication link 478 and can communicate with eitherorbital satellite group 150 or orbital satellite group 151 oversatellite communication link 477. Airborne node 430 can optionallycommunicate with parent node 110 over communication link 479.

Satellite communication links 471-477 each comprise communication linkssimilar to those discussed above for satellite communication links175-178, although variations are possible. Terrestrial communicationlink 480 comprises one or more links similar to that discussed above forcommunication links 124, 134, 144, although variations are possible.Communication links 478-479 comprise wireless RF links or optical links.Examples of links 478-479 include WiFi, WiMAX, microwave RFcommunications, High Frequency (HF), VHF, or UHF communications links,including combinations thereof.

In operation, parent node 110 establishes a network arrangement thatincludes communication nodes comprising parent node 110, child node 120,and child node 420. This network arrangement is represented by satelliteedge network (SEN) 402 in FIG. 4, which may be similar to SEN 102 inFIG. 1 in some examples. In FIG. 4, parent node 110 is configured toestablish SEN 402 over at least a satellite communication pathway withone or more child nodes remotely located from a geographic location ofparent node 110. Parent node 110 establishes SEN 402 by at leastestablishing a network transport layer for the child node over one ormore link layers provided by the satellite communication pathways. Thenetwork transport layer can comprise a virtual transport layer ortransport layer formed over a transport layer or layers of the varioussatellite communication links coupling parent node 110 to the childnodes. SEN 402 comprises a network transport layer separate from or inaddition to any provided by satellite communication service providers.SEN 402 is thus formed over one or more of the various satellitecommunication links included in FIG. 4. SEN 402 can span over one ormore satellite communication links, one or more satellite groups orsatellite communication service providers, and one or more child nodes.To couple into SEN 402, each communication node employs an associatedsatellite communication link or satellite communication link incombination with one or more airborne communication links. However, eachindividual satellite communication link might experience various changesin link properties or link status over time. Parent node 110 maintainsSEN 402 over various changes in link properties or link pathway. SEN 402tolerates changes in link properties or link pathways while maintainingthe network arrangement. Thus, a fault-tolerant and link-independentnetwork arrangement is employed in FIG. 4. For example, parent node 110is configured to maintain SEN 402 with the child nodes after at leastone of the child nodes changes from communicating over a first satellitecommunication pathway provided by a first satellite communicationservice provider to communicating over a second satellite communicationpathway provided by a second satellite communication service provider.Specifically, child node 120 might initially communicate over link 473via orbital satellite group 150 and change to communicate over link 474via orbital satellite group 151. Alternatively, child node 120 mightinitially communicate over link 473 via orbital satellite group 150 andchange to communicate over a merged or aggregated pathway that comprisesboth link 474 and link 474. Similar operation can occur for parent node110 with respect to links 470-472 and 479, or with child node 420 withrespect to links 476 and 478.

SEN 402 can be configured to support network packet routing, networkpacket transfer, and network packet handling over the various linksshown in FIG. 4 as if parent node 110, child node 120, and child node420 were all on a locally-connected network that shares a transportlayer. To provide such an arrangement, various network transportprotocols can be employed, such as encrypted layered tunneling protocolsor virtual private networks (VPNs). Example transport protocols includeInternet Protocol Security (IPsec), Transport Layer Security (SSL/TLS),virtual LANs (VLANs), IEEE 802.1Q, Pseudo Wire (PW), Point-to-PointTunneling Protocol (PPTP), or Virtual Private LAN Service (VPLS), amongothers. In some examples, the aforementioned network transport protocolsmight be modified or enhanced to support satellite communication linksor links of airborne nodes, as well as changes to properties or pathwaysof the underlying physical links.

Turning now to one example operation for the elements of FIG. 4, childnode 420 might initially communicate over SEN 402 using satellitecommunication link 476, orbital satellite group 151, and link 471.However, due to changes in the properties of link 476 or changes inrequirements of one or more applications executed at child node 420,child node 420 might be triggered to change link properties or linkpathways. Changes in the link properties might include any of theaforementioned link property changes, such as fading or loss in signalquality for link 476. Other examples include jamming conditions, whichmay be passive, active, intentional, or unintentional. The examples canalso include movement of one or more satellite devices of orbitalsatellite group 151 to prevent continued communication over link 476.The link properties might be monitored by link manager 425 of child node420 and identify the changes or triggers. Responsive to these changes ortriggers, link manager 425 can initiate one or more alternativecommunication pathways to reach parent node 110 and remain communicatingon SEN 402. A first example alternative communication pathway includeslink 480 which couples child node 420 to child node 120. In this firstalternative, traffic can be routed over link 480 to child node 120 whichcan responsively route this traffic over any associated link from whichchild node 120 couples into SEN 402. A second example alternativecommunication pathway includes link 478 which is established withairborne node 430. Airborne node 430 has connectivity to SEN 402 oversatellite communication link 477 which might be provided by orbitalsatellite group 150 or 151. In this second alternative, traffic can berouted over link 478, airborne node 430, and link 477 to reach anorbital satellite group with which parent node 110 presently hasconnectivity. A third example alternative communication pathway includeslinks 478-479 which are established by airborne node 430. Airborne node430 has connectivity to parent node 110 over communication link 479. Inthis third alternative, traffic can be routed over link 478, airbornenode 430, and link 479 to reach parent node 110 presently hasconnectivity. One or more further airborne or terrestrial nodes andlinks can be included to reach parent node 110 or child node 420. Thus,in these examples, child node 420 can maintain presence within SEN 402even if the various communication pathways change. The network transportlayer arrangement employed by parent node 110 to establish SEN 402 canbe altered with each change in communication pathway to allow fortraffic to be correctly routed to the associated endpoints. This caninclude updating network addressing, network routes, or virtual LANproperties to reflect the new communication pathways.

Turning now to another example operation for the elements of FIG. 4,application requirements of one or more of the applications 127 deployedto child node 120 might request additional communication bandwidth oradditional communication quality/reliability. Also, one or more objectnodes 421-423 might request additional communication bandwidth oradditional communication quality/reliability. Policy engine 126 of childnode 120 can identify these requests and associated bandwidthrequirements. Once identified, policy engine 126 can trigger changes toone or more among links 473-474 to support the bandwidth requests. Inone instance, child node 120 is initially communicating over satellitecommunication link 473 and link 474 is idle or not presentlyestablished. In another instance, child node 120 is initiallycommunicating over satellite communication link 474 and link 473 is idleor not presently established. To add the additional bandwidth, linkmanager 125 can change link properties of one or more active links, oradd additional links for traffic. The changes in link properties caninclude increasing a transfer rate of the link, changing linkfrequencies, changing a transmit power, changing link bondingconfigurations, selecting a different satellite device which has ahigher quality link potential, changing satellite communication servicesprovider to one which has a higher quality link potential, altering adata or signal compression scheme, or altering a communication codingscheme to allow for additional bandwidth for user traffic (such as toreduce a quantity of accompanying error correction traffic), among otherchanges, including combinations thereof. Alternatively, link manager 125can add one or more additional satellite communication links to increasea communication bandwidth. This is shown in FIG. 4 as creating anaggregated or merged link 475. The aggregation of the bandwidth of links473-474 into link 472 can occur at various points in a network stack. Inone example, a transport layer or higher layer is employed to aggregatebandwidth of two or more links. In another example, such as shown belowin FIG. 5, an additional layer between a link layer and transport layeris employed to aggregate bandwidth of two or more links. Theaforementioned changes to link properties or link quantities can also beapplied to the operation of parent node 110 with regard to links470-472.

Advantageously, the arrangement shown in FIG. 4 provides for enhancednetwork connectivity and network flexibility for object nodes 421-423 totransfer and receive traffic with regard to parent node 110 over SEN402. Various link pathway changes and link property changes can occurwhile maintaining network connectivity within SEN 402 for parent node110, child node 120, child node 420, and object nodes 421-423. Moreover,selection among various satellite communication service providers can bemade on-the-fly to best suit the communication needs or requests of oneor more applications or object nodes.

FIG. 5 illustrates protocol stack arrangement 501 according to animplementation. Communication layers 510-519 might be employed in anetwork arrangement that forms at least portions of SEN 102 or SEN 402.Also included in FIG. 5 is traffic management 502 and bandwidthaggregation example 503.

A first layer (L1) in the protocol stack comprises two physical layers(phy1, phy2) each associated with a separate physical media, such asseparate satellite communication links. If more than two concurrentlinks are employed, then further corresponding physical layers can beincluded at L1. At L1, each physical layer 510-511 is separate andcorresponds to a physical pathway used to communicate data bits over alink with a satellite device. The physical layer can include RF oroptical transmissions using various amplitude, power, coding, frequency,channel, and modulation properties.

A second layer (L2) includes one or more link layers (link1, link2) eachassociated with different satellite communication links. At L2 inarrangement 501, each link layer 512-513 is separate and corresponds totransmission of frames of data which can include some low-levelretransmission or physical layer error handling. The frames associatedwith L2 include sender and receiver media access control (MAC)addresses, among other identifiers.

An intermediate layer (L2X) between L2 and L3 is included in FIG. 5. L2Xlayer 514 can optionally be employed by a communication node toaggregate bandwidth of the separate satellite communication linksassociated with physical layers 510-511 and link layers 512-513. Inlayer L2X, a bandwidth can be combined from among two satellitecommunication links which might be provided by different satellitecommunication service providers or different satellite devices.Functionality of layer L2X can include ordering of data frames receivedover more than one physical link, and merging of ordered data framesinto an aggregate stream of data frames from more than one physicallink, among other functionality. To provide this functionality, variouscircuitry or software can be included in a communication node thatprovides for combining communication bandwidth of two or more separatephysical links into a single network layer or transport layer. This mayinclude buffering of frames received over more than one physical linkand inspection of frame headers or packet headers to determine orderingamong the frames of the more than one physical links. In one example, asource communication node might form a stream of data frames whichincludes header fields or ordering indicators in addition to any of theframes to establish an ordering among the frames in the stream beforetransfer of the frames over different physical links. L2X can inspectthese ordering indicators to order the frames received over separatephysical links and merge the frames into a single stream of frames foruse by higher layers in the protocol stack.

In one example, shown as bandwidth aggregation example 503, two separatephysical links each have an associated center frequency or transmissionfrequency (F1, F2). Each link has an associated bandwidth (B1, B2) whichcorresponds to a quantity or rate of data able to be transferred overthe link in ideal conditions. The amount of RF energy for each link isshown in example 503 as RF energy curves 531-532. When combining oraggregating the bandwidth for two links, an increased total bandwidth isshown (B3) which corresponds to RF energy curve 530. Thus, two RF linksmight coexist at a single communication node, as shown for the separatephysical/link layers in protocol stack arrangement 501, and theircombined bandwidth can be used to provide for enhanced execution andhandling of applications deployed to the communication node. Other formsof link aggregation might be employed, such as aggregation at higherlayers in protocol stack arrangement 501 using various logical orvirtualized arrangements.

A third layer (L3) in the protocol stack comprises network layer 515,and is typically responsible for packet forwarding, routing, and packetaddressing. One example L3 protocol includes the Internet Protocol (IP)which employs network addresses (IPv4 or IPv6) for data arranged intopackets.

A fourth layer (L4) in the protocol stack comprises transport layer 516,and coordinates data transfer between system and hosts, performserror-checking, and performs some data recovery. One example L4 protocolincludes transmission control protocol/user datagram protocol (TCP/UDP),which employs port numbers, sequence numbers, flow control for segmentsof data packets.

In FIG. 5, layers 5-7 can include standard network protocol features, aswell as specialized and enhanced features shown in traffic management502. A fifth layer (L5) in the protocol stack comprises session layer517 that establishes and terminates connections between devices, and canperform segregation of packets into separate groups, such as files. Asixth layer (L6) in the protocol stack comprises presentation layer 518that translates between data formatting employed by applications anddata formatting used by the lower level networking protocols. A seventhlayer (L7) in the protocol stack comprises application layer 519 whichinterfaces with user-level applications. However, in addition to thestandard functionality discussed above, layers L5-L7 in FIG. 5 includeadditional functionality and virtualization features shown in trafficmanagement 502.

Traffic management 502 includes several components which provideadditional services at the L5-L7 layer to network data packets/frameswith regard to user applications or data 520 which produce networkworkloads 522. A first set of components of traffic management 502 isnetwork services 521. Network services provide various workload handlingfeatures including prioritization among workloads 522, carrier-grade(CG) network address translation (NAT) that provides sharing of groupsof network addresses among many endpoints, network traffic filteringoperations, wide-area network options, traffic/port firewalls, and otherfeatures for handling of network traffic with regard to networkworkloads 522. A second set of components of traffic management 502 isnetwork virtualization 523. Network virtualization 523 handles creationand management of one or more virtual network arrangements 524. Virtualnetwork arrangements 524 can include virtual private networks (VPNs),virtual local area networks (VLANs), virtual extensible LANs (VXLANs),or other virtualized network arrangements to support user applicationsor data 520 which may comprise one or more virtualized applications ordistributed data as will be discussed below. A third set of componentsof traffic management 502 is management services 525. Management service525 can manage any of the modules or features of traffic management 502,such as network services 521, network workloads 522, or networkvirtualization 523. Management services 525 includes manual or automaticdeployment of any of the features of traffic management 502,orchestration of network resources and features of traffic management502, and general management features related to traffic management 502.

Turning now to several examples related to application deployment andchild node management, FIG. 6 is presented. FIG. 6 illustratescommunication environment 600 according to an implementation.Environment 600 includes parent node 110, child node 120, child node130, packet communication system 160, and data service 161. Although notshown for clarity in FIG. 6, parent node 110 and child nodes 120 and 130will typically have one or more communication links to handlecommunications between and among the nodes, such as the satellitecommunication links seen in FIG. 1, or variations thereof. Parent node110 also communicates with packet communication system 160 overcommunication link 170. Data service 161 illustrates an example cloudcomputing, distributed data storage, or data handling service which maybe employed by other elements of environment 600. Data service 161communicates over communication link 171. In FIG. 6, several elementsfound in FIG. 1 are included, along with additional elements used toillustrate further example implementations. However, it should beunderstood that the examples in FIG. 6 are not limited to the elementsfound in FIG. 1.

In FIG. 6, parent node 110 is shown including pool resource manager 611.Pool resource manager 611 comprises circuitry or software which isconfigured to discover physical resources local to each child node,catalog such resources, and manage deployment of such resources. Thephysical resources can include processing resources or computingresources, as indicated by data processing capacity, data processor typeand quantity, as well as current workload handled by the dataprocessors. The data processors might include central processing units(CPUs), microprocessors, graphics processing units (GPUs), TensorProcessing Units (TPUs), deep-learning processors and circuitry,embedded processors, microcontrollers, and other types of dataprocessing circuitry. The physical resources can include data storageresources, as indicated by data storage capacity (total or free space),as well as storage media type. Data storage resources might include harddisk drives (HDDs), solid state storage drives (SSDs), hybrid diskdrives, optical storage drives, magnetic storage devices, or otherstorage media and devices. The physical resources can includecommunication resources or communication link resources, as indicated bycommunication interface types, quantities, and available bandwidths. Thecommunication interfaces can be of the various types discussed herein,including RF communication interfaces, satellite communicationinterfaces, optical communication interfaces, local and remotecommunication interfaces, Ethernet or other local network interfaces,local wireless interfaces, and other communication interfaces. Thephysical resources can include object nodes, as indicated by object nodetypes, object node devices, sensor types, telemetry resources, telemetrydata availability, properties of the object nodes, communicationbandwidth of the object nodes, telemetry bandwidth, sample frequency, orother features of the object nodes. Other physical resources can bediscovered and cataloged by parent node 110 for each child node, andupdates to the discovery and cataloging process can be performed on acyclic or periodic basis, as well as in response to changes inconfigurations of the child nodes.

Pool resource manager 611 can maintain one or more data structures withindications of the physical resources corresponding to each child nodeand current status of availability of the physical resources. Poolresource manager 611 might establish a pool of resources which can beemployed for use in execution of various applications deployed to thechild nodes. The pool of resources can comprise a pool of free or unusedresources, and pool resource manager 611 can track resources which havebeen allocated or assigned from the free pool for use by activities of achild node. In operation, one or more users or operators may wish todeploy applications to one or more child nodes for use of the localphysical resources of the child node or to employ one or more objectnodes for various tasks. In addition, the child nodes themselves ordevices coupled thereto may initiate activities which prompts executionof an application by a child node or retrieval of data by the childnode. FIGS. 8A and 8B below discuss operations of these pools ofresources in more detail.

However, deployment of the applications to child nodes can be brieflydiscussed in the context of FIG. 6. In FIG. 6, one or more applicationrequests can be initiated by data service 161. Data service 161 mayinclude one or more front-ends, user interfaces, or applicationprogramming interfaces (APIs) which allow users or operators to selectand initiate applications for deployment to one or more child nodes.These applications may comprise various types of applications whichemploy the physical resources of target child nodes. Child nodes mightbe selected based on availability of physical resources, which mayinclude both location-dependent physical resources, or selected based onwhich physical resources are free to perform activities of theapplications. Location-dependent physical resources can include sensors,telemetry devices, or IoT devices which have a geographic locationdesirable to the user deploying the applications, such as sensors whichsense a particular locality/area, telemetry devices for particularpieces of equipment, or IoT devices specific a location of the childnode.

In a first example, one or more applications 620 may be requested fordeployment by data service 161. Data service 161 may communicate withparent node 110 over links 170-171 and network 160 to indicate therequest for deployment of applications 620. The request may be for aspecifically indicated application or applications, or may instead be arequirements-based request that indicates particular sensorrequirements, telemetry requirements, processing requirements,communication requirements, storage requirements, or other requirements.When the requests indicate specific applications for deployment, thenpool resource manager 611 of parent node 110 can select one or morechild nodes which shall receive deployed applications. When the requestsindicate requirements, then pool resource manager 611 of parent node 110can select among the child nodes based on availability of physicalresources which meet or exceed the requirements. Parent node 110 canthen deploy applications 620 over the associated LAN and satellitecommunication links to one or more child nodes for execution. In FIG. 6,applications 620 are received from data service 161, but other examplesmight have parent node 110 retrieve the applications from one or morestorage systems instead. FIG. 6 shows two child nodes (120, 130)receiving applications 620. Thus, configuration 680 is shown in whichapplications 620 span two locations and child nodes. Applications 620can execute using local resources of each child node, which are selectedamong computing resources, storage resources, communication resources,and object node resources. Once applications 620 are deployed, poolresource manager 611 can reflect a current usage of the physicalresources of the child nodes by removing these physical resources fromthe free pool of resources.

In a second example, data might be pushed to the edge for caching of thedata by one or more child nodes. Data 621 might be initially requestedby users or devices (e.g. object nodes) coupled to a first child node,such as child node 120. This data can include user data, files, usercontent, web content, images, video, configuration data, applicationdata, or other various data types. Parent node 110 can retrieve data 621from one or more data sources, such as data service 161. Once receivedinto parent node 110, parent node 110 can deploy data 621 to one or morechild nodes over the associated LAN and satellite communication links.Child node 120 can receive data 621 and store data 621 within one ormore storage devices local to child node 120. One or more users, objectnodes, or applications associated with child node can then consume data621. Once cached or stored in child node 120, other child nodes mightrequest one or more portions of data 621. These requests can be receivedby parent node 110. Parent node 110 can determine that data 621 isalready cached by child node 120 and indicate to the other child node,such as child node 130, that data 621 can be provided by child node 120.Thus, child node 130 can request data 621 from child node 120 instead offrom data service 161. Data 621 can be transferred between the childnodes using parent node 110 as an intermediary, such as over a LAN orsatellite communication links which couple the child nodes and parentnode 110.

In some examples, child node 130 might have one or more othercommunication interfaces, such as terrestrial communication interfacesor local communication interfaces (wired or wireless) which canfacilitate a more direct transfer of data 621 from child node 120 tochild node 130. FIG. 7 illustrates terrestrial communication links770-771 which are suitable for direct transfers. Data 621 might bestored at child node 120 until no longer needed by any child node, whichmight include a predetermined amount of time after a last-receivedrequest for data 621, or data 621 may be removed from child node 120 ifother data has been requested at a later time which supersedes data 621,among other configurations. Data 621 might also be preemptively cachedin one or more child nodes based on applications which have beendeployed to the child nodes, or based on past activity patterns forparticular child nodes, among other preemptive triggers for data cachingat the ‘edge’ provided by child nodes. Furthermore, the applicationsdeployed to a first child node might perform data caching activitiesinitiated responsive to user activity of a first requestor object nodecoupled via a local communication interface to the first child node. Thefirst child node can be configured to serve cached data to at least asecond requestor object node. The second requestor object node could belocated at the first child node or at a second child node.

In a third example, one or more applications are deployed to child nodeswhich perform telemetry, monitoring, sensing, or other activities whichgenerates data at object nodes or the child node. The associated childnode can temporarily cache or store this locally-generated data prior totransfer to one or more recipient systems. Alternatively, parent node110 can perform caching duties for outgoing data and collect this datafrom one or more child nodes prior to transfer to further entities. Thedata can be stored until favorable conditions warrant transfer. Thesemight include considering the status or properties of one or moresatellite communication links that couple the child nodes, parent node,or other packet networks. For example, a current bandwidth of one ormore satellite communication links might not support transfer of datagenerated by a child node, and that child node can cache such data untilthe bandwidth exceeds a target threshold. In another example, parentnode 110 waits to transfer data until a predetermined amount has beencollected in parent node 110, providing for a large burst transfer ofdata instead of many smaller transfers. Other configurations can beemployed for temporary collection and caching of outgoing data generatedat the child nodes.

Many of the examples discussed herein employ software applications, suchas applications 127 in FIG. 1, user applications 520 in FIG. 5,applications 620 in FIG. 6, and applications 720 in FIG. 7, amongothers. In these examples, the software applications may be deployed asa collection of files, configuration data, and other metadata for nativeexecution by a processing system using an operating system deployed to achild node. However, the software applications may instead be deployedand executed as virtualized software assemblies, referred to herein asvirtual nodes. These virtual nodes may comprise full operating systemvirtual machines in some examples, and may further include virtualcontainers. These containers may include Docker containers, Linuxcontainers, jails, or another similar type of virtual containment node,which can provide an efficient management of resources in a targetsystem which executes the virtual node. The resources used by thecontainers may include kernel resources from the target system, and mayinclude repositories and other resources that are approved to be sharedwith other containers or processes executing on the target system.Although resources may be shared between the containers on a targetsystem, the containers might be provisioned to have private access tothe operating system with a separate identifier space, file systemstructure, and communication interface.

A more detailed discussion on management and operation of physicalresources at child nodes is now presented. FIG. 7 includes schematicview 700 of a pool of resources formed using resources found at threeexemplary child nodes 120, 130, and 140. Pool resource manager 611 ofparent node 110 can establish and manage this pool of resources. Eachchild node has a collection of object nodes coupled thereto over acorresponding local communication interface, namely object nodes121-123, 131-133, and 141-143, which have been discussed above. Eachchild node typically includes various physical resources, such asprocessing resources, data storage resources, and communicationresources. Each object node coupled to a child node will have acorresponding set of features defined in part by included circuitry,hardware, software, and other elements which provide a particularfunctionality of the corresponding object node.

Moreover, view 700 includes a terrestrial communication links 770-771which facilitate more direct communication of data or applicationsbetween child nodes. Terrestrial communication links 770-771 cancomprise any link discussed herein for links 124, 134, 144, and 170-172of Figure, among other link types. View 700 also includes 5Gcommunication node 750 which provides for an alternate terrestrialcommunication link 772 for child node 140 in addition to satellitecommunication interface 183. Although FIG. 7 employs a 5G cellularcommunications link defined by the 3GPP consortium, other cellular orterrestrial like types discussed herein can be employed, includingearlier-defined and later-defined cellular link, protocol, and networkconfigurations such as 3G and 4G, or 6G and beyond. 5G node 750 may belocated at a different geographic location than that of child node 140,but still remain in communication proximity. 5G node 750 can be furthercoupled to one or more other 5G nodes or to backhaul links coupled to acellular communication network or assorted packet communicationnetworks.

Turning now to example operations for the elements of FIG. 7, flowdiagrams are provided in FIGS. 8A and 8B. The operations of FIGS. 8A and8B are discussed in the context of both FIG. 6 and FIG. 7, althoughsimilar functionality can be provided by any of the correspondingelements in the other Figures. Operations 800 of FIG. 8A focus onoperations of a parent node, while operations 850 FIG. 8B focus onoperations of a child node.

Turning first to FIG. 8A, pool resource manager 611 of parent node 110establishes (810) a pool of child node resources, noted in FIG. 7 aspool of resources 780. Pool resource manager 611 can be configured todetermine physical resources local to each of the plurality of childnodes, and establish pool of resources 780 from among the physicalresources. Pool resource manager 611 can perform a discovery process bypolling each child node to discover what physical resources are presentat each child node, from among resources of each child node and that oflocally-coupled object nodes. This polling can include querying theplurality of child nodes over corresponding satellite communicationlinks to assemble the pool of resources from among the physicalresources at each of the plurality of child nodes. Pool resource manager611 can maintain one or more data structures with indications of thephysical resources corresponding to each child node and current statusof availability of the physical resources. Pool of resources 780 cancomprise a pool of free or unused resources, and pool resource manager611 can track resources which have been allocated or assigned from thefree pool for use by activities of a child node.

Pool resource manager 611 determines (811) one or more applications fordeployment to child nodes at the ‘edge’ of a communication system formedamong at least a parent node and child nodes. One or more users oroperators may wish to deploy applications to one or more child nodes foruse of the local physical resources of the child node or to employ oneor more object nodes for various tasks. In addition, the child nodesthemselves or devices coupled thereto may initiate activities whichprompts execution of an application by a child node or retrieval of databy the child node. The applications can be identified responsive torequests for execution of an application, which could be received fromexternal users, child nodes, or object nodes.

Responsive to the requests, either a user/operator or pool resourcemanager 611 selects (812) child nodes at the edge for deployment of theapplications, and allocates corresponding resources from pool ofresources 780 for execution of the applications at one or more selectedchild nodes. In operation 811, the applications might perform monitoringactivities employing object node resources, such as employing sensordevices, telemetry devices, or IoT devices included at the one or moreselected child nodes. The applications might also include communicationactivities employing communication link resources included at the one ormore selected child nodes to relay data collected by the object noderesources. The applications might comprise one or more virtual nodeswhich are deployed from a storage system managed by parent node 110 ordata service 161-162. These virtual nodes can be received by theselected child nodes and stored locally for execution by a processingsystem a virtualized execution system of the child nodes. In thismanner, many applications can be deployed to each child node and thevirtual nodes can each have segregated access to the relevant physicalresources of the child node. Sharing of resources among child nodesmight occur in certain cases, such as when a hypervisor system of thechild node can manage sharing of memory, processor, storage, andcommunication resources among many virtual nodes. Sharing of object noderesources among virtual nodes can also be managed in a similar fashion.

Sometimes resources might be available at child nodes, but theseresources might not configured properly in a current state to supportactivities of the applications. Pool resource manager 611 can directselected child nodes to alter the state of the resources to supportactivities of the desired applications. In one example, pool resourcemanager 611 can be configured to identify properties of at least a firstsatellite communication link associated with a first child node todetermine if the first satellite communication link supports activitiesof the application with regard to the first child node. Responsive tothe first satellite communication link determined to not support theactivities, pool resource manager 611 can be configured to instruct thefirst child node to alter the first satellite communication link tosupport the activities of the application. The alteration might includealtering properties of the satellite communication link or addinganother satellite communication link, such as discussed above withregard to FIG. 2. In this manner, child nodes can be instructed toprovide sufficient network connectivity over the corresponding satellitecommunication links to object nodes (e.g. one or more user devices orone or more sensor devices) coupled over local communication interfacesof the child nodes.

In other instances (813), resources of a single child node might not besufficient to support the activities of the applications. In theseinstances, pool resource manager 611 can be configured to span theapplications over more than one child node. Pool resource manager 611might select physical resources across more than one child node forexecution of the application. Pool resource manager 611 can thentransfer at least a portion of an application to each of the selectedchild nodes, such as by transferring a copy of the application to two ormore child nodes or deploying a virtual node to more than one child nodeto consume resources at each child node. If only one child node issufficient for execution of the application, then pool resource manager611 can deploy (814) the application to a selected child node fromparent node 110. Responsive to deployment of the applications, theassociated child nodes initiate execution of the applications using theallocated resources at the one or more selected child nodes.

Pool resource manager 611 also removes the allocated resources from poolof resources 780 until at least completion of execution of theapplication. For example, pool resource manager 611 can monitor (816) ifthe deployed applications or deployed data are still needed at the edgeor at associated child nodes. If the resources are determined to nolonger be needed for an application, then pool resource manager 611returns (817) resources to pool of resources 780.

In further examples, during execution of the applications by at least afirst child node, pool resource manager 611 can be configured to monitorutilization of resources of the first child node associated withexecution of the application. Responsive to the utilization exceeding athreshold level, pool resource manager 611 can be configured to shift(817) at least a portion of the application for execution by a secondchild node to reduce the utilization of resources of the first childnode. This shifting of workload might occur responsive to utilizationsmentioned above, but might instead occur responsive to disruption incommunications or connectivity of the child nodes that have theapplications deployed thereto. State information related to currentexecution of the applications can be relayed by the child nodes to theparent node. Pool resource manager 611 might maintain data structuresand storage elements with the state information of currently executingapplications or currently deployed applications. Responsive todisruptions in operation of the child nodes, the associated resources,or communication links, pool resource manager 611 can transfer or shiftone or more deployed applications, data, or workloads to another childnode. The parent node hosting pool resource manager 611 might be anintermediary for the transfer or shift or pool resource manager 611 mayinstead instruct one or more child nodes to transfer theworkload/application/data directly to another child node over anassociated communication interface. Once transferred, applications orworkloads can utilize resources of the new child node and beginexecution according to state information. The state information might betransferred along with the workload, application, or data. In addition,any data transferred can be stored local to the new child node and madeavailable for access to other nodes or users from that child node.

FIG. 7 includes a specific example of application or data deploymentthat spans child nodes. Application 720 and data 721-722 are indicatedin FIG. 7. Application 720 can comprise a distributed application thatspans resources of more than one child node, such as distributed dataprocessing applications, distributed virtualization activities,distributed data storage activities, or distributed data communicationsrouting activities for routing communications of object nodes.Application 720 and data 721-722 might be deployed to one or moreselected child nodes for execution and usage of local resources (such asstorage resources) of the selected child nodes. For example, data 721might be deployed by parent node 110 to child node 120 over one or moresatellite communication links that form SEN 102 or SEN 402. Data 722might be generated at child node 130 and shared or served by child node130 over one or more satellite communication links that form SEN 102 orSEN 402. Data 721-722 might be deployed to a first child node and thenrelayed over links 770-771 to another child node, or to other nodes,including object nodes and users.

Application 720 is shown as deployed to more than one child node,specifically, child nodes 130 and 140. Application 720 consumesresources included at both child node 130 and child node 140, such ascomputing, storage, communication, or object resources. The objectresources might comprises sensor elements, telemetry elements, or IoTelements which are located at both child node 130 and child node 140.For example, application 720 might employ these spanned resources toleverage sensor resources across more than one child node. Parent node110 can deploy portions of application 720 to each of child node 130 andchild node 140. Child node 130 and child node 140 might exchangecommunications related to operations of application 720 over acorresponding LAN.

In addition to the factors for application deployment and data storagediscussed herein, quality of service (QoS) can be taken into account.For example, deployment of applications to child nodes might considerQoS of the communication links used to deploy the applications, QoS ofcommunication links that might service data generated or consumed by theapplications, or QoS of resources local to the child nodes, such as QoSof object nodes. Parent node 110 might monitor QoS metrics for variouschild nodes and communication links associated with the child nodesbefore deployment of the applications or data. When selecting whichchild nodes should receive deployed applications or data, parent node110 might consider QoS among other factors to select specific childnodes that can support the application execution requirements,communication link requirements, storage requirements, or othertask-specific needs. Also, when shifting workloads, parent node 110 orany associated child node might trigger shifting of workloads based onQoS metrics indicating that certain applications or data services arenot having specified QoS levels being met. Thus, in operation 817,shifting of workloads might take into account not only the performanceor status of a child node, but QoS specified for the workload.

Turning now to FIG. 8B and operations 850, functionality of resourcemanagement at the edge is discussed. The ‘edge’ refers primarily tofunctionality at the child nodes or object nodes. In FIG. 7, each ofchild nodes 120, 130, and 140 has a local resource manager, indicated byedge resource managers 712-714. These edge resource managers can beexamples of edge resource manager 1027 of FIG. 10, although variationsare possible. In FIG. 8B, process connector 820 links operations of FIG.8A to FIG. 8B. Typically, the operations of FIG. 8B are relevant onceapplications or data have been deployed to child nodes by a parent node.However, the operations of FIG. 8B might occur without the initialdeployment of a parent node, such as when a child node has pre-existingapplications/data or object-node initiated applications or data.

Child nodes 120, 130, and 140 can provide associated local resources forexecution of deployed applications at the edge, as well as storage ofdata at the edge. These resources can include any of the various childnode or object node resources discussed herein. Once deployed, theapplications or data might be in an active, inactive, or throttledstate, and when virtualized execution platforms like hypervisors areemployed, then applications can be initiated using virtual nodes.Moreover, child nodes 120, 130, and 140 have a limited amount ofresources which might be shared among users, object nodes, orapplications. FIG. 8B relates to how to manager these limited resourcesand adapt to dynamic conditions at the edge.

In operation 860, a child node receives deployment instructions forapplications or data. These instructions might include indications andpolicies on what resources are required for execution of theapplication, such as processing, storage, or communication resourcesalong with applicable bandwidths, latencies, or other parameters. Theseinstructions can be employed by policy engines of the child nodes toestablish which resources are allocated (861) to which applications ordata. Edge resource managers 712-714 can then monitor (862) theresources of the corresponding child nodes in regard to the deployedapplications and data. Edge resource managers 712-714 can establishvarious triggers which alter a state of execution or state of allocatedresources, such as by triggering a start, stop, or throttling ofapplications or data. In FIG. 8B, these triggers can include linkresources triggers (863), time triggers (865), and workload triggers(867). Since edge resource managers 712-714 have visibility to theresources of the particular child node, decisions on allocation of thoseresources can be made locally to the child node. Data can be parsed todetermine which data has a higher priority or critical property so as tobe transferred or stored ahead of other data. Various data can becategorized among high priority, medium priority, and low priority orbest effort data. Applications may have similar categorization forexecution and resource utilization.

A link resource trigger (863) can include triggers based on propertiesof communication links affecting a child node, such as communicationlink bandwidth, communication link latency, communication link typeavailability, or other communication link properties. For example, asatellite link for a child node might experience reduced bandwidth dueto movement of associated satellite devices, atmospheric fading,interference, or other conditions and influences. A threshold forbandwidth can be established for one or more applications deployed tothe child node, and when the bandwidth of a particular link falls belowthe threshold bandwidth, then an edge resource manager can reallocateresources, initiate further communication links, or throttle/stop anapplication until the bandwidth conditions improve. Likewise, if acommunication link has properties which do not presently supportexecution of an application, then the edge resource manager can holdthat application idle until bandwidth conditions improve. Thus, edgeresource managers 712-714 of child nodes can alter (864) resources ordeployment associated with applications or data to compensate forchanges in link properties. In further examples, a child node mightcollect and cache data generated by one or more object nodes, such astelemetry data from the object nodes. This telemetry data can be heldfrom transfer until one or more bandwidth triggers are met, and once metthe data can be burst transferred over a corresponding communicationlink to the parent node, another child nodes, or for transfer to furtherendpoints.

A time trigger (865) can include triggers based on time of day or day ofthe week, among other temporal triggers. These triggers might includeperiodic timers, peak activity detection, or other triggers. Edgeresource managers 712-714 can monitor the time or day, among otherparameters, and adjust resources according to these parameters.Applications and data might reside at a child node in an idle,throttled, or inactive state until a particular time, with resources ofthe child node assigned to other workloads or to other tasks. Edgeresource managers 712-714 can activate the applications or begin toservice/serve the data responsive to time triggers being satisfied.Moreover, edge resource managers 712-714 can activate or deploy (866)resources of the child nodes once the time triggers have been satisfied.In further examples, a child node might collect and cache data generatedby one or more object nodes, such as telemetry data from the objectnodes. This telemetry data can be held from transfer until one or moretime triggers are met, and once met the data can be burst transferredover a corresponding communication link to the parent node, anotherchild nodes, or for transfer to further endpoints.

A workload trigger (867) can include triggers based on local resourceutilization of the child nodes, and can be related to link resourceutilization. The resources might include local network utilization,processor utilization, memory utilization, storage utilization, or otherlocal resource utilization. Edge resource managers 712-714 can deployapplications or data in the child nodes based on changes in workloads.For example, when a first application is executing and using resourcesof a child node, other applications might be throttled or wait untilthat first application has ceased execution or entered an idle modebefore the other applications ramp up on such resources. Moreover,resources might be overutilized at a child node and edge resourcemanagers 712-714 might shift (868) the workloads among child nodes tobalance the loading of local resources of affected child nodes. Thisshifting of workloads can include capturing a state of execution orstate of processing for affected applications and transferring the stateto other child nodes for execution of the corresponding applications.The applications themselves also might be transferred to the other childnodes when the applications have not yet been deployed to those childnodes.

Advantageously, edge resource managers 712-714 can handle allocation andusage of local resources of child nodes without involvement of theparent node once the applications and data have been deployed to theedge. Various intelligent decisions can be made at the edge as to whatapplications are executed, what data is stored and transferred, and whenall of these activities can occur based on local conditions of the childnodes. As these conditions change over time, edge resource managers712-714 can adjust the execution of workloads, shift execution ofworkloads, assign/allocate resources, and transfer data, among otheractivities.

FIG. 9 illustrates parent node 910 that is representative of any systemor collection of systems from which the various operations discussedherein for parent nodes can be directed, including child node discovery,child node control, satellite communication link control, satellitelink-based LAN establishment, pool resource management, andapplication/data deployment, among other operations. Any of theoperational architectures, platforms, scenarios, and processes disclosedherein may be implemented using elements of parent node 910. In oneimplementation, parent node 910 is representative of at least a portionof parent node 110 of FIG. 1. In some examples, child node 910 comprisesan enhanced very small aperture terminal (VSAT).

Parent node 910 may be implemented as a single apparatus, system, ordevice or may be implemented in a distributed manner as multipleapparatuses, systems, or devices. Parent node 910 includes, but is notlimited to, processing system 911, communication interface system 912,storage system 913, random access memory (RAM) 914, and software 920.Processing system 911 is operatively coupled with storage system 913 andcommunication interface system 912. Communication interface system 912includes one or more specialized communication interfaces, such assatellite communication interface 950 which can communicate over one ormore satellite communication links 955, and terrestrial communicationinterface 970 which can communicate over one or more terrestrialcommunication links 975.

Processing system 911 loads and executes software 920 from storagesystem 913. When executed by processing system 911, software 920 directsprocessing system 911 to operate as described herein for at least thevarious processes, operational scenarios, and sequences discussed in theforegoing implementations. Parent node 910 may optionally includeadditional devices, features, or functionality not discussed forpurposes of brevity. Processing system 911 may comprise a microprocessorand processing circuitry that retrieves and executes software 920 fromstorage system 913. Processing system 911 may be implemented within asingle processing device, but may also be distributed across multipleprocessing devices, sub-systems, or specialized circuitry, thatcooperate in executing program instructions and in performing theoperations discussed herein. Examples of processing system 911 includegeneral purpose central processing units, application specificprocessors, and logic devices, as well as any other type of processingdevice, combinations, or variations thereof.

Storage system 913 may comprise any computer readable storage mediareadable by processing system 911 and capable of storing software 920.Storage system 913 may include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information, such as computer readable instructions, data structures,program modules, or other data. Examples of storage media include randomaccess memory (RAM) 914, read only memory, magnetic disks, opticalstorage media, flash memory, HDDs, SSDs, virtual memory and non-virtualmemory, magnetic storage media, or any other suitable storage media.Storage system 913 may be implemented as a single storage device, butmay also be implemented across multiple storage devices or sub-systemsco-located or distributed relative to each other. Storage system 913 maycomprise additional elements, such as a controller, capable ofcommunicating with processing system 911 or possibly other systems.

Software 920 may be implemented in program instructions. When executedby processing system 911, software 920 directs processing system 911 tooperate as described with respect to the various operational scenarios,sequences, and processes illustrated herein. For example, software 920may include program instructions for providing enhanced child nodediscovery, child node control, satellite communication link control,satellite link-based LAN establishment, pool resource management, andapplication/data deployment, among other operations. In particular, theprogram instructions of software 920 may include various components ormodules that cooperate or otherwise interact to carry out the variousprocesses and operational scenarios described herein. The variouscomponents or modules may be embodied in compiled or interpretedinstructions, or in some other variation or combination of instructions.The various components or modules may be executed in a synchronous orasynchronous manner, serially or in parallel, in a single threadedenvironment or multi-threaded, or in accordance with any other suitableexecution paradigm, variation, or combination thereof. Software 920 mayinclude additional processes, programs, or components, such as operatingsystem software, hypervisor components, applications, or other software.Software 920 may also comprise program code, scripts, macros, and othersimilar components. Software 920 may also comprise software or someother form of machine-readable processing instructions executable byprocessing system 911.

Software 920 may, when loaded into processing system 911 and executed,transform a suitable apparatus, system, or device (of which parent node910 is representative) overall from a general-purpose computing systeminto a special-purpose computing system customized to facilitate atleast child node discovery, child node control, satellite communicationlink control, satellite link-based LAN establishment, pool resourcemanagement, and application/data deployment operations. Encodingsoftware 920 on storage system 913 may transform the physical structureof storage system 913. The specific transformation of the physicalstructure may depend on various factors in different implementations ofthis description. Examples of such factors may include, but are notlimited to, the technology used to implement the storage media ofstorage system 913 and whether the computer-storage media arecharacterized as primary or secondary storage, as well as other factors.For example, if the computer readable storage media are implemented assemiconductor-based memory, software 920 may transform the physicalstate of the semiconductor memory when the program instructions areencoded therein, such as by transforming the state of transistors,capacitors, or other discrete circuit elements constituting thesemiconductor memory. A similar transformation may occur with respect tomagnetic or optical media. Other transformations of physical media arepossible without departing from the scope of the present description,with the foregoing examples provided only to facilitate the presentdiscussion.

Software 920 can include one or more software elements, such as anoperating system, device drivers, hypervisor or virtualization elements,and one or more applications. For example, an operating system andhypervisor 921 can provide a software platform on which storage softwareelements 922-926 are executed. Operating system/hypervisor 921 iscapable of providing a platform for virtual nodes according to animplementation. Operating system/hypervisor 921 is representative of avirtualized execution system, which includes a virtualized user spacefor virtual nodes 922, an operating system or hypervisor, a storagespace in storage system 913 to store the operating system and virtualuser space, and processing resources of processing system 911.

Users, operators, or organizations may generate applications that arecapable of being deployed as virtual nodes on one or more parent nodesor child nodes. These applications may be provided from a data servicessystem, storage system, or may be provided from another communicationnode. Once the applications are provided, operating system/hypervisor921, which is stored on storage system 913 and executed by processingsystem 911 may provide a platform for the execution of the applications.Here, each application provided to parent node 910 is executed asseparate virtualized software assemblies, referred to as virtual nodesand shown as virtual nodes 922. Virtual nodes 922 may comprise fulloperating system virtual machines or containers capable of sharingresources from the underlying operating system in storage system 913.

Operating system/hypervisor 921 manages the execution of virtual nodes922, and may manage a schedule that is used to allocate processingresources of processing system 911, communication resources ofcommunication interface system 912, and storage resources of storagesystem 913 to each of virtual nodes 922. In particular, the schedule maybe used to ensure that each application is scheduled to receiveprocessing resources from processing system 911 during defined timeperiods, and receive access to communication interface system 912 duringdefined time periods. In some implementations, one or more of theapplications may execute during the same time period on parent node 910.These applications may use different resources of parent node 910 (orlocally coupled devices), may time share the use of resources of parentnode 910, or may use the same data in their operation. To allocate theresources of parent node 910, operating system/hypervisor 921 may beresponsible for providing each operating virtual node with accessinformation for the required resources of parent node 910, anddeallocating or removing the access to the required resources of parentnode 910 based on the scheduling. For example, a resource may beaccessed by a first of virtual nodes 922 during a first time period,where the first of virtual nodes 922 may access the resource based onaccess information provided by operating system/hypervisor 921. Once thetime period expires, operating system/hypervisor 921 may prevent thefirst of virtual nodes 922 from accessing the resource. In someexamples, this may occur by removing the access for the first of virtualnodes 922, and allocating access of the resource to a second of virtualnodes 922.

In addition to applications deployed as virtual nodes 922, otherapplications and functionality is provided by software 920. These otherapplications and functionality are indicated by edge deployer 923, poolresource manager 924, link manager 925, and child node tracker 926. Edgedeployer 923, pool resource manager 924, link manager 925, and childnode tracker 926 can be deployed and executed as native applications, orinstead as separate virtual nodes, similar to that discussed above forvirtual nodes 922.

Edge deployer 923 can transfer at least a portion of an application toone or more child node over satellite communication links, deploy one ormore virtual nodes to child nodes over satellite communication links forexecution by the child nodes, and deploy one or more virtual nodes tochild nodes over a local area network for execution of at least anapplication that spans resources of more than one child node. Edgedeployer 923 can deploy data for caching by one or more child node, andapplications for caching by one or more child node.

Pool resource manager 924 can establish a pool of resources, selectphysical resources across more than one child node for execution of anapplication, allocate resources from a pool of resources for executionof an application at one or more selected child nodes and remove theallocated resources from the free pool of resources until at leastcompletion of execution of the application. Pool resource manager 924can select physical resources across more than one child node forexecution of an application. Pool resource manager 924 can initiateexecution of an application using the allocated resources at one or moreselected child nodes. Pool resource manager 924 can identify propertiesof at least a first satellite communication link associated with a firstchild node to determine if the first satellite communication linksupports activities of an application with regard to a child node, andresponsive to the first satellite communication link determined to notsupport the activities, instruct the child node to alter the firstsatellite communication link. During execution of an application by atleast a child node, pool resource manager 924 can monitor utilization ofresources of a child node associated with execution of the application.Responsive to the utilization exceeding a threshold level, pool resourcemanager 924 can shift at least a portion of an application for executionby a subsequent child node to reduce the utilization of resources of aninitial child node.

Link manager 925 can establish a local area network over at least asatellite communication pathway with one or more child nodes. Linkmanager 925 can establish the local area network by at leastestablishing a network transport layer for child nodes over one or morelink layers provided by the satellite communication pathway. Linkmanager 925 can maintain the local area network with a child node afterthe child node changes to communicating over a second satellitecommunication pathway provided by a second satellite communicationservice provider. Link manager 925 can route at least a portion of datarelated to the operation of the one or more local telemetry devices toat least one additional child node coupled to the local area networkover an additional satellite communication pathway.

Child node tracker 926 can perform various discovery processes todiscover child nodes for inclusion into an arrangement with a parentnode. Child node tracker 926 can receive indications of child nodes thatare desired to be included in an arrangement with a parent node. Childnode tracker 926 can determine physical resources local to each of aplurality of child nodes, query the plurality of child nodes overcorresponding satellite communication links to assemble a pool ofresources from among the physical resources at each of the plurality ofchild nodes. Child node tracker 926 can monitor utilization of resourcesof a child node associated with execution of application.

Communication interface system 912 may include communication connectionsand elements that allow for communication over links 955 and 975 withother external systems (not shown in FIG. 9) over one or morecommunication links or networks (not shown). Links 955 can use optical,air, or space as the transport media. Links 975 can use metal, glass,optical, air, space, or some other material as the transport media.Links 955 and 975 can be direct links or may include intermediatenetworks, systems, or devices, and can include a logical network linktransported over multiple physical links. Other example links not shownin FIG. 9 which might be used separately or in combination with theabove include discrete control links, system management buses, serialcontrol interfaces, register programming interfaces, applicationprogramming interfaces (APIs), network interface cards, and othercommunication software and circuitry. Communication interface system 912may communicate over communication media to exchange communications withother computing systems or networks of system. Communication interfacesystem 912 may include user interface elements, such as programmingregisters, control/status registers, APIs, web interfaces, displayinterfaces, or other user-facing control and status elements.

Satellite communication interface 950 is configured to communicate overone or more satellite communication links 955 to support at leastcommunications with satellite devices to reach one or more child nodes.Satellite communication interface 950 comprises one or moretransceivers, antennas, antenna arrays, dish antennas, antenna feedelements, signal splitters, RF or optical amplifiers, low-noise blockdownconverters (LNBs), low-noise downconverters (LNDs), blockupconverters (BUCs), satellite trackers, phased antenna arrays, antennamotor mounts, and other RF or optical communication circuitry andequipment. Satellite communication interface 950 can employ variouscommunication interface types and protocols discussed herein. Satellitecommunication interface 950 may utilize a frequency range correspondingto the IEEE bands of L band, S band, C band, X band, Ku band, Ka band, Vband, W band, among others. Other example communication frequency rangesinclude Ultra high frequency (UHF), super high frequency (SHF),extremely high frequency (EHF), or other service categories such asbroadcast satellite service (BSS), fixed-satellite service (FSS),mobile-satellite service (MSS) or similar services for broadcastcommunications.

In addition to the preceding discussion, satellite communicationinterface 950 can include any of the elements discussed in FIG. 10 forsatellite communication interface 1050. Additionally, more than oneinstance of satellite communication interface 950 can be included inparent node 910, with each instance capable of communicating over aseparate satellite communication link. The separate satellitecommunication links can be with different satellite devices, differentorbital satellite groups, and different satellite communication serviceproviders. Separate aiming of antennas, dish elements, phased arrays,beamforming, and the like can support the multiple different satellitecommunication links.

Terrestrial communication interface 970 is configured to communicateover one or more communication links 975 to support at leastcommunications with one or more external systems, cloud systems,distributed data systems, or packet networks, or with one or moreairborne communication nodes. Terrestrial communication interface 970comprises one or more transceivers, antennas, antenna arrays, RF oroptical amplifiers, airborne node trackers, phased antenna arrays,optical aiming apparatuses, and other RF or optical communicationcircuitry and equipment. Terrestrial communication interface 970 canemploy various communication interface types and protocols, such asInternet Protocol (IP) versions 4 or 6, Ethernet, universal serial bus(USB), Wireless USB, Peripheral Component Interconnect Express (PCIe),Thunderbolt, Bluetooth, IEEE 802.11 (WiFi), WiMAX (WorldwideInteroperability for Microwave Access), microwave RF communications, VHFcommunications, UHF communications, low-power wide-area network (LPWAN),LoRa (Long Range), low-rate wireless personal area networks (LR-WPANs),IEEE 802.15.4 (Zigbee, among others), Near-field communication (NFC),Infrared Data Association (IrDA), hybrid fiber-coax (HFC), synchronousoptical networking (SONET), asynchronous transfer mode (ATM), TimeDivision Multiplex (TDM), Long-Term Evolution (LTE), 3rd GenerationPartnership Project (3GPP)-defined protocols, 5G or 5G NR (New Radio)communications, or other communication signaling or communicationformats, including combinations, improvements, or variations thereof.

FIG. 10 illustrates child node 1010 that is representative of any systemor collection of systems from which the various operations discussedherein for child nodes can be directed, including object node discoveryand management, satellite communication link control, deployedapplication execution, pool resource reporting, and edgedata/application caching, among other operations. Any of the operationalarchitectures, platforms, scenarios, and processes disclosed herein maybe implemented using elements of child node 1010. In one implementation,child node 1010 is representative of at least a portion of child nodes120, 130, 140 of FIG. 1, or child node 420 of FIG. 4. In some examples,child node 1010 comprises an enhanced very small aperture terminal(VSAT).

Child node 1010 may be implemented as a single apparatus, system, ordevice or may be implemented in a distributed manner as multipleapparatuses, systems, or devices, which may include virtualizedportions. Child node 1010 includes, but is not limited to, processingsystem 1011, communication interface system 1012, storage system 1013,random access memory (RAM) 1014, and software 1020. Processing system1011 is operatively coupled with storage system 1013 and communicationinterface system 1012. Communication interface system 1012 includes oneor more specialized communication interfaces, such as satellitecommunication interfaces 1050 which can communicate over one or moresatellite communication links 1055, terrestrial communication interface1070 which can communicate over one or more terrestrial communicationlinks 1075, and object communication interface 1080 can communicate overone or more object communication links 1085.

Processing system 1011 loads and executes software 1020 from storagesystem 1013. When executed by processing system 1011, software 1020directs processing system 1011 to operate as described herein for atleast the various processes, operational scenarios, and sequencesdiscussed in the foregoing implementations. Child node 1010 mayoptionally include additional devices, features, or functionality notdiscussed for purposes of brevity. Processing system 1011 may comprise amicroprocessor and processing circuitry that retrieves and executessoftware 1020 from storage system 1013. Processing system 1011 may beimplemented within a single processing device, but may also bedistributed across multiple processing devices, sub-systems, orspecialized circuitry, that cooperate in executing program instructionsand in performing the operations discussed herein. Examples ofprocessing system 1011 include general purpose central processing units,application specific processors, and logic devices, as well as any othertype of processing device, combinations, or variations thereof.

Storage system 1013 may comprise any computer readable storage mediareadable by processing system 1011 and capable of storing software 1020.Storage system 1013 may include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information, such as computer readable instructions, data structures,program modules, or other data. Examples of storage media include randomaccess memory (RAM) 1014, read only memory, magnetic disks, opticalstorage media, flash memory, HDDs, SSDs, virtual memory and non-virtualmemory, magnetic storage media, or any other suitable storage media.Storage system 1013 may be implemented as a single storage device, butmay also be implemented across multiple storage devices or sub-systemsco-located or distributed relative to each other. Storage system 1013may comprise additional elements, such as a controller, capable ofcommunicating with processing system 1011 or possibly other systems.

Software 1020 may be implemented in program instructions. When executedby processing system 1011, software 1020 directs processing system 1011to operate as described with respect to the various operationalscenarios, sequences, and processes illustrated herein. For example,software 1020 may include program instructions for providing enhancedobject node discovery and management, satellite communication linkcontrol, deployed application execution, pool resource reporting, andedge data/application caching, among other operations. In particular,the program instructions of software 1020 may include various componentsor modules that cooperate or otherwise interact to carry out the variousprocesses and operational scenarios described herein. The variouscomponents or modules may be embodied in compiled or interpretedinstructions, or in some other variation or combination of instructions.The various components or modules may be executed in a synchronous orasynchronous manner, serially or in parallel, in a single threadedenvironment or multi-threaded, or in accordance with any other suitableexecution paradigm, variation, or combination thereof. Software 1020 mayinclude additional processes, programs, or components, such as operatingsystem software, hypervisor components, applications, or other software.Software 1020 may also comprise program code, scripts, macros, and othersimilar components. Software 1020 may also comprise software or someother form of machine-readable processing instructions executable byprocessing system 1011.

Software 1020 may, when loaded into processing system 1011 and executed,transform a suitable apparatus, system, or device (of which child node1010 is representative) overall from a general-purpose computing systeminto a special-purpose computing system customized to facilitate atleast object node discovery and management, satellite communication linkcontrol, deployed application execution, pool resource reporting, andedge data/application caching operations. Encoding software 1020 onstorage system 1013 may transform the physical structure of storagesystem 1013. The specific transformation of the physical structure maydepend on various factors in different implementations of thisdescription. Examples of such factors may include, but are not limitedto, the technology used to implement the storage media of storage system1013 and whether the computer-storage media are characterized as primaryor secondary storage, as well as other factors. For example, if thecomputer readable storage media are implemented as semiconductor-basedmemory, software 1020 may transform the physical state of thesemiconductor memory when the program instructions are encoded therein,such as by transforming the state of transistors, capacitors, or otherdiscrete circuit elements constituting the semiconductor memory. Asimilar transformation may occur with respect to magnetic or opticalmedia. Other transformations of physical media are possible withoutdeparting from the scope of the present description, with the foregoingexamples provided only to facilitate the present discussion.

Software 1020 can include one or more software elements, such as anoperating system, device drivers, hypervisor or virtualization elements,and one or more applications. For example, an operating system andhypervisor 1021 can provide a software platform on which storagesoftware elements 1022-1027 are executed. Operating system/hypervisor1021 is capable of providing a platform for virtual nodes according toan implementation. Operating system/hypervisor 1021 is representative ofa virtualized execution system, which includes a virtualized user spacefor virtual nodes 1022, an operating system or hypervisor, a storagespace in storage system 1013 to store the operating system and virtualuser space, and processing resources of processing system 1011. Software1020 might also include other elements, such as firewalls, resourceorchestration interfaces and algorithms, encryption modules,authentication modules, and other features.

Users, operators, or organizations may generate applications that arecapable of being deployed as virtual nodes on one or more parent nodesor child nodes. These applications may be provided from a data servicessystem, storage system, or may be provided from another communicationnode. Once the applications are provided, operating system/hypervisor1021, which is stored on storage system 1013 and executed by processingsystem 1011 may provide a platform for the execution of theapplications. Here, each application provided to child node 1010 isexecuted as separate virtualized software assemblies, referred to asvirtual nodes and shown as virtual nodes 1022. Virtual nodes 1022 maycomprise full operating system virtual machines or containers capable ofsharing resources from the underlying operating system in storage system1013.

Operating system/hypervisor 1021 manages the execution of virtual nodes1022, and may manage a schedule that is used to allocate resources toeach of virtual nodes 1022, such has processing resources of processingsystem 1011, communication resources of communication interface system1012, storage resources of storage system 1013, and object noderesources of connected object nodes. In particular, the schedule may beused to ensure that each application is scheduled to receive resourcesduring defined time periods. In some implementations, one or more of theapplications may execute or share resources during the same time periodon child node 1010. These applications may use different resources ofchild node 1010 (or locally coupled devices), may time share the use ofresources of child node 1010, or may use the same data in theiroperation. To allocate the resources of child node 1010, operatingsystem/hypervisor 1021 may be responsible for providing each operatingvirtual node with access information for the required resources of childnode 1010 or object node resources of connected object nodes, anddeallocating or removing the access to the required resources based onthe scheduling. For example, a resource may be accessed by a first ofvirtual nodes 1022 during a first time period, where the first ofvirtual nodes 1022 may access the resource based on access informationprovided by operating system/hypervisor 1021. Once the time periodexpires, operating system/hypervisor 1021 may prevent the first ofvirtual nodes 1022 from accessing the resource. In some examples, thismay occur by removing the access for the first of virtual nodes 1022,and allocating access of the resource to a second of virtual nodes 1022.

In addition to applications deployed as virtual nodes 1022, otherapplications and functionality is provided by software 1020. These otherapplications and functionality are indicated by application cache 1023,data cache 1024, policy engine 1025, link manager 1026, and edgeresource manager 1027. Application cache 1023, data cache 1024, policyengine 1025, link manager 1026, and edge resource manager 1027 can bedeployed and executed as native applications, or instead as separatevirtual nodes, similar to that discussed above for virtual nodes 1022.

Application cache 1023 provides for caching of applications in a localstorage system of child node 1010, such as in storage system 1013.Application cache 1023 provides for deployment of the cachedapplications to object nodes, child node 1010, or to other child nodesover terrestrial communication interface 1070 or object communicationinterface 1080. Data cache 1024 provides similar caching features asapplication cache 1023, but for data and content requested by objectnodes, child node 1010, or to other child nodes over terrestrialcommunication interface 1070 or object communication interface 1080.Application cache 1023 or data cache 1024 can perform caching responsiveto requests for the applications or data, or can instead preemptivelycache data based on deployed applications or historical patterns. Datacache 1024 might cache data generated by one or more applicationsexecuted by a child node, and hold/store that data until transfer toanother child node, parent node, or other endpoint. Quality of serviceof the resources of the child node or communication links can beconsidered for initiating transfer of data stored in data cache 1024.For example, particular policies might be control times for transfer ofdata from data cache 1024, such as times of day according to policies,when communication bandwidths exceed threshold levels, when localresources of a child node fall below certain utilization thresholdlevels, or when other parameters indicated by a user dictate changessuch as temporal (time of day, day of week, etc.), financial (linkcosts), or other characteristics. These policies can operate fortransfers of data from data cache 1024, or for transfer of data intodata cache 1024 for use by the local child node or object nodes.

Policy engine 1025 can provide data related to operation of one or morelocal object nodes, such as sensors, telemetry devices, or IoT devices,over a local area network for receipt by a parent node. Policy engine1025 can parse at least a first portion of data related to operation ofone or more local object nodes and route the first portion of the dataover a second local communication interface for alert of activitiesrelated to the operation of the one or more local object nodes. Policyengine 1025 can identify communication requirements related to executionof one or more applications by child node 1010. Policy engine 1025 caninitiate changes to one or more satellite communication links based atleast on application communication requirements and properties of theone or more satellite communication links. Policy engine 1025 canprocess one or more triggers to initiate changes to the one or moresatellite communication links. Policy engine 1025 can initiate at leasta second satellite communication link over a second satellitecommunication service provider different than a first satellitecommunication service provider to accommodate at least applicationcommunication requirements. Policy engine 1025 can direct link manager1026 to discontinue a satellite communication link and communicate overa second satellite communication link, direct link manager 1026 toestablish a combined communication bandwidth associated with a firstsatellite communication link and a at least one additional satellitecommunication link, and provide a combined communication bandwidth to atleast an application associated with the application communicationrequirements. Responsive to changes in the properties of one or moresatellite communication links indicating a communication link qualityfalling below a quality threshold, policy engine 1025 can select adifferent communication pathway than an initial satellite communicationlink to accommodate at least the communication requirements. Thedifferent communication pathway may comprise a communication linkprovided by an airborne node that has link availability with at leastone among a satellite communication network and a terrestrialcommunication network. Responsive to changes in properties of one ormore satellite communication links indicating a communication linkquality falling below a quality threshold, policy engine 1025 canidentify at least one among a different communication frequency,different communication coding scheme, different data or signalcompression scheme, different beam direction, and different satellitecommunication service provider to accommodate at least the communicationrequirements.

Link manager 1026 can communicate over one or more satellitecommunication links provided by at least a satellite communicationservice provider. Link manager 1026 can monitor properties of the one ormore satellite communication links. Link manager 1026 can establish alocal area network over at least a satellite communication pathway,communicate over at least the satellite communication pathway toestablish a connection to the local area network and routecommunications of a local communication interface to the local areanetwork.

Edge resource manager 1027 can establish management of child noderesources, select physical resources of a child node for execution of anapplication, allocate child node resources for execution of anapplication, monitor current conditions of child nodes, and triggervarious shifting or adjustment of workloads, execution, or otheractivities. Edge resource manager 1027 can identify properties of atleast a first satellite communication link associated with a child nodeto determine if the first satellite communication link supportsactivities of an application with regard to the child node, andresponsive to the first satellite communication link determined to notsupport the activities, instruct the child node to alter the firstsatellite communication link or adjust execution of the application tosuit the available properties of the first satellite communication link.During execution of an application, edge resource manager 1027 canmonitor utilization of resources of a child node associated withexecution of the application. Responsive to the utilization exceeding athreshold level, edge resource manager 1027 can shift at least a portionof an application for execution by a subsequent child node to reduce theutilization of resources of an initial child node. Edge resource manager1027 can perform other activities as discussed in FIG. 8B for edgeresource managers 712-714.

Communication interface system 1012 may include communicationconnections and elements that allow for communication over links 1055,1075, and 1085 with other external systems (not shown in FIG. 10) overone or more communication links or networks (not shown). Links 1055 canuse optical, air, or space as the transport media. Links 1075 and 1085can use metal, glass, optical, air, space, or some other material as thetransport media. Links 1055, 1075, and 1085 can be direct links or mayinclude intermediate networks, systems, or devices, and can include alogical network link transported over multiple physical links. Otherexample links not shown in FIG. 10 which might be used separately or incombination with the above include discrete control links, systemmanagement buses, serial control interfaces, register programminginterfaces, application programming interfaces (APIs), network interfacecards, and other communication software and circuitry. Communicationinterface system 1012 may communicate over communication media toexchange communications with other computing systems or networks ofsystem. Communication interface system 1012 may include user interfaceelements, such as programming registers, control/status registers, APIs,web interfaces, display interfaces, or other user-facing control andstatus elements.

Satellite communication interface 1050 is configured to communicate overone or more satellite communication links 1055 to support at leastcommunications with satellite devices to reach parent nodes or otherchild nodes. Satellite communication interface 1050 comprises one ormore transceivers, antennas, antenna arrays, dish antennas, antenna feedelements, signal splitters, RF or optical amplifiers, low-noise blockdownconverters (LNBs), low-noise downconverters (LNDs), blockupconverters (BUCs), satellite trackers, phased antenna arrays, antennamotor mounts, and other RF or optical communication circuitry andequipment. Satellite communication interface 1050 can employ variouscommunication interface types and protocols discussed herein. Satellitecommunication interface 1050 may utilize a frequency range correspondingto the IEEE bands of L band, S band, C band, X band, Ku band, Ka band, Vband, W band, among others. Other example communication frequency rangesinclude ultra high frequency (UHF), super high frequency (SHF),extremely high frequency (EHF), or other service categories such asbroadcast satellite service (BSS), fixed-satellite service (FSS),mobile-satellite service (MSS) or similar services for broadcastcommunications. In addition to the preceding discussion, satellitecommunication interface 1050 can include any of the elements discussedin FIG. 10 for satellite communication interface 1050.

A detailed view of one example implementation of satellite communicationinterface 1050 is shown in view 1001 in FIG. 10. View 1001 showssatellite communication interface 1050 as including software definedradio (SDR) 1051 and antenna interface (UF) 1060. More than one instanceof satellite communication interface 1050 will typically be included inchild node 1010, with each instance capable of communicating over aseparate satellite communication link. The separate satellitecommunication links can be with different satellite devices, differentorbital satellite groups, and different satellite communication serviceproviders. Separate aiming of antennas, dish elements, phased arrays,beamforming, and the like can support the multiple different satellitecommunication links.

SDR 1051 includes forward error correction (FEC) element 1052, systemtiming element 1053, and multiplexer (MUX) 1054. FEC element 1052 cancorrect for various bit errors in communications received by child node1010 or transmitted by child node 1010. Data is fed into FEC element1052 during uplink operations to encode the data with error correctionbits. Received bits are fed into FEC element 1052 during downlinkoperations to decode the data using error correction bits and correctfor one or more bit errors. System timing element 1053 comprises timingcircuitry, clock circuitry, modulation circuitry, and can performvarious transmit/receive or uplink/downlink timing operations among theelements of SDR 1051 and antenna interface 1060, which might includedetermining and enforcing protocol-specific orfrequency/channel-specific timing parameters and modulation parameters.System timing element 1053 can control up conversion/down conversionfrequencies and operations of upconverter 1061 and downconverter 1063.Multiplexer 1054 comprises multiplexor circuitry and handlesmultiplexing among uplink/downlink data as well as control instructionsfor control of the elements of satellite communications interface 1050.

Antenna interface 1060 includes upconverter 1061, control circuit 1062,downconverter 1063, transmitter/uplink antenna interface 1064, orthomodetransducer (OMT) 1065, receiver/downlink antenna interface 1066, antennafeed element 1067, antenna management element 1068, and dish/antenna1069. Control circuit 1062 can control up conversion/down conversionfrequencies and operations of upconverter 1061 and downconverter 1063,and can receive associated control parameters from system timing element1053. Control circuit 1062 can control operations of transmitter/uplinkantenna interface 1064 and receiver/downlink antenna interface 1066.Upconverter 1061 includes oscillator circuitry, phase-locked loop (PLL)circuitry, and frequency reference circuitry to convert a signal havinga first functional frequency to a signal having a second, typicallyhigher, RF frequency. Upconverter 1061 can comprise one or more blockupconverters (BUCs). Downconverter 1063 includes oscillator circuitry,PLL circuitry, and frequency reference circuitry to convert a signalhaving a first RF frequency to a signal having a second, typicallylower, functional frequency. Downconverter 1063 may comprise one or morelow-noise block downconverters (LNBs) or low-noise downconverters(LNDs). OMT 1065 is configured to combine or to separate twoorthogonally polarized RF signal pathways. A first signal pathway of OMT1065 corresponds to an uplink pathway, and a second pathway of OMT 1065corresponds to a downlink pathway.

Transmitter/uplink antenna interface 1064 comprises a portion of theuplink pathway, and receiver/downlink antenna interface 1066 comprises aportion of the downlink pathway. Transmitter/uplink antenna interface1064 can include RF power amplifiers, transceiver circuitry, antennainterface circuitry, and other elements. Receiver/downlink antennainterface 1066 can include transceiver circuitry, receiver circuitry,antenna interface circuitry, and other elements. Antenna feed element1067 comprises a feed antenna which sources RF energy to dish/antenna1069. Antenna feed element 1067 can receive RF energy from a transmitteras well. Antenna feed element 1067 may comprise a feed horn.Dish/antenna 1069 comprises one or more parabolic dish elements andcouples mechanically to antenna feed element 1067. Although a dish styleof antenna is discussed in FIG. 10, other types of directional antennasor beam antennas can be employed, such as antenna arrays, Yagi antennas,log-periodic (LP) antennas, reflector antennas, active antennas such asactive phased arrays (APA), electronically steered arrays, or variationsthereof. Antenna management element 1068 can control orientation,direction, and aiming of one or more dish elements or feed elements.Antenna management element 1068 may orient antenna elements based onlocations of target satellite devices using various electromechanicalactuators, such as motors, servos, gimbals, rotors, and the link. Whenphased array antenna devices are employed, antenna management element1068 might instead control active elements of the phased array orperform additional tilt operations for the phased array.

Terrestrial communication interface 1070 is configured to communicateover one or more communication links 1075 to support at leastcommunications with one or more external systems, other child nodes, orwith one or more airborne communication nodes. Terrestrial communicationinterface 1070 comprises one or more transceivers, antennas, antennaarrays, RF or optical amplifiers, airborne node trackers, phased antennaarrays, optical aiming apparatuses, and other RF or opticalcommunication circuitry and equipment. Terrestrial communicationinterface 1070 can employ various communication interface types andprotocols, such as Internet Protocol (IP) versions 4 or 6, Ethernet,universal serial bus (USB), Wireless USB, Peripheral ComponentInterconnect Express (PCIe), Thunderbolt, Bluetooth, IEEE 802.11 (WiFi),WiMAX (Worldwide Interoperability for Microwave Access), microwave RFcommunications, VHF communications, UHF communications, low-powerwide-area network (LPWAN), LoRa (Long Range), low-rate wireless personalarea networks (LR-WPANs), IEEE 802.15.4 (Zigbee, among others),Near-field communication (NFC), Infrared Data Association (IrDA), hybridfiber-coax (HFC), synchronous optical networking (SONET), asynchronoustransfer mode (ATM), Time Division Multiplex (TDM), Code DivisionMultiplex (CDM), Code Division Multiple Access (CDMA), ChaoticWaveforms, Long-Term Evolution (LTE), 3rd Generation Partnership Project(3GPP)-defined protocols, 5G or 5G NR (New Radio) communications, orother communication signaling or communication formats, includingcombinations, improvements, or variations thereof.

Object node communication interface 1080 is configured to communicateover one or more communication links 1085 to support at leastcommunications with one or more object nodes local to child node 1010.Object node communication interface 1080 comprises one or moretransceivers, antennas, antenna arrays, RF or optical amplifiers, andother RF or optical communication circuitry and equipment. Object nodecommunication interface 1080 can employ various communication interfacetypes and protocols, such as Internet Protocol (IP) versions 4 or 6,Ethernet, universal serial bus (USB), Wireless USB, Peripheral ComponentInterconnect Express (PCIe), Thunderbolt, Bluetooth, IEEE 802.11 (WiFi),WiMAX (Worldwide Interoperability for Microwave Access), microwave RFcommunications, VHF communications, UHF communications, low-powerwide-area network (LPWAN), LoRa (Long Range), low-rate wireless personalarea networks (LR-WPANs), IEEE 802.15.4 (Zigbee, among others),Near-field communication (NFC), Infrared Data Association (IrDA), hybridfiber-coax (HFC), synchronous optical networking (SONET), asynchronoustransfer mode (ATM), Time Division Multiplex (TDM), Long-Term Evolution(LTE), 3rd Generation Partnership Project (3GPP)-defined protocols, 5Gor 5G NR (New Radio) communications, or other communication signaling orcommunication formats, including combinations, improvements, orvariations thereof.

The included descriptions and figures depict specific implementations toteach those skilled in the art how to make and use the best option. Forthe purpose of teaching inventive principles, some conventional aspectshave been simplified or omitted. Those skilled in the art willappreciate variations from these implementations that fall within thescope of the disclosure. Those skilled in the art will also appreciatethat the features described above can be combined in various ways toform multiple implementations. As a result, the invention is not limitedto the specific implementations described above, but only by the claimsand their equivalents.

What is claimed is:
 1. A computing node, comprising: a communication interface configured to communicate with a plurality of child nodes over corresponding satellite communication links; and a resource manager configured to: determine physical resources local to each of the plurality of child nodes; establish a pool of resources from among the physical resources; responsive to a request for execution of an application, allocate resources from the pool of resources for execution of the application at one or more selected child nodes; and initiate execution of the application using the allocated resources at the one or more selected child nodes.
 2. The computing node of claim 1, wherein the physical resources comprise processing resources, storage resources, communication link resources, and telemetry resources.
 3. The computing node of claim 1, wherein the application comprises monitoring activities employing sensor resources included at the one or more selected child nodes, and communication activities employing communication link resources included at the one or more selected child nodes to relay data collected by the sensor resources.
 4. The computing node of claim 1, wherein the application comprises data caching activities initiated responsive to user activity of a first requestor node coupled via a local communication interface to a first child node, and wherein the first child node is configured to serve cached data to at least a second requestor node.
 5. The computing node of claim 1, comprising: the resource manager configured to select physical resources across more than one child node for execution of the application; and the resource manager configured to transfer at least a portion of the application to each of the more than one child node over ones of the satellite communication links.
 6. The computing node of claim 1, comprising: the resource manager configured to query the plurality of child nodes over the corresponding satellite communication links to assemble the pool of resources from among the physical resources at each of the plurality of child nodes; and responsive to the request for execution of the application, the resource manager configured to remove the allocated resources from the free pool of resources until at least completion of execution of the application.
 7. The computing node of claim 1, wherein the child nodes provide network connectivity over the corresponding satellite communication links to one or more user devices or one or more sensor devices coupled over local communication interfaces of the child nodes, and wherein the one or more user devices and the one or more sensor devices comprise the physical resources.
 8. The computing node of claim 1, comprising: the resource manager configured to identify properties of at least a first satellite communication link associated with a first child node to determine if the first satellite communication link supports activities of the application with regard to the first child node; and responsive to the first satellite communication link determined to not support the activities, the resource manager configured to instruct the first child node to alter the first satellite communication link.
 9. The computing node of claim 1, comprising: during execution of the application by at least a first child node, the resource manager configured to monitor utilization of resources of the first child node associated with execution of the application; and responsive to the utilization exceeding a threshold level, the resource manager configured to shift at least a portion of the application for execution by a second child node to reduce the utilization of resources of the first child node.
 10. A method of operating a computing node, the method comprising: communicating with a plurality of child nodes over corresponding satellite communication links; determining physical resources local to each of the plurality of child nodes; establishing a pool of resources from among the physical resources; responsive to a request for execution of an application, allocating resources from the pool of resources for execution of the application at one or more selected child nodes; and initiating execution of the application using the allocated resources at the one or more selected child nodes.
 11. The method of claim 10, wherein the physical resources comprise processing resources, storage resources, communication link resources, and telemetry resources.
 12. The method of claim 10, wherein the application comprises monitoring activities employing sensor resources included at the one or more selected child nodes, and communication activities employing communication link resources included at the one or more selected child nodes to relay data collected by the sensor resources.
 13. The method of claim 10, wherein the application comprises data caching activities initiated responsive to user activity of a first requestor node coupled via a local communication interface to a first child node, and wherein the first child node is configured to serve cached data to at least a second requestor node.
 14. The method of claim 10, further comprising: selecting physical resources across more than one child node for execution of the application; and transferring at least a portion of the application to each of the more than one child node over ones of the satellite communication links.
 15. The method of claim 10, further comprising: querying the plurality of child nodes over the corresponding satellite communication links to assemble the pool of resources from among the physical resources at each of the plurality of child nodes; and responsive to the request for execution of the application, removing the allocated resources from the free pool of resources until at least completion of execution of the application.
 16. The method of claim 10, wherein the child nodes provide network connectivity over the corresponding satellite communication links to one or more user devices or one or more sensor devices coupled over local communication interfaces of the child nodes, and wherein the one or more user devices and the one or more sensor devices comprise the physical resources.
 17. The method of claim 10, further comprising: identifying properties of at least a first satellite communication link associated with a first child node to determine if the first satellite communication link supports activities of the application with regard to the first child node; and responsive to the first satellite communication link determined to not support the activities, instructing the first child node to alter the first satellite communication link.
 18. The method of claim 10, further comprising: during execution of the application by at least a first child node, monitoring utilization of resources of the first child node associated with execution of the application; and responsive to the utilization exceeding a threshold level, shifting at least a portion of the application for execution by a second child node to reduce the utilization of resources of the first child node.
 19. An apparatus, comprising: one or more computer readable storage media; a processing system operatively coupled with the one or more computer readable storage media; and program instructions stored on the one or more computer readable storage media that, based on being read and executed by the processing system, direct the processing system to at least: communicate with a plurality of child nodes over corresponding satellite communication links; determine physical resources local to each of the plurality of child nodes; establish a pool of resources from among the physical resources; responsive to a request for execution of an application, allocate resources from the pool of resources for execution of the application at one or more selected child nodes; and initiate execution of the application using the allocated resources at the one or more selected child nodes.
 20. The apparatus of claim 19, comprising further program instructions, based on being executed by the processing system, direct the processing system to at least: select physical resources across more than one child node for execution of the application; and transfer at least a portion of the application to each of the more than one child node over ones of the satellite communication links. 